r/Base44

Hey r/Base44 👋

Your community team is doing an AMA - and we want to hear from you.

We're u/Base44_Sam and u/Sammy_Base, the two Sams behind Base44's community. Between us we're building in the open, supporting builders, and spending more time in this subreddit than is probably healthy.

Drop your questions below - we'll be answering live on Friday 10th July at 15:00 UTC, but feel free to get them in early. We'll be working through everything in the thread.

No topic is off limits. Community, product, what we're building, what it's actually like behind the scenes. Ask us anything.

See you Friday!

What are some sites you guys have built or have seen that are built (at least mostly) with base44?

Also, would you say the platform is better for mobile or web apps in general?

Does anyone have experience getting a web app into the App Store? I’m trying to get mine approved ASAP, but right now it uses Stripe for payments, and I know Apple has rules about that. What’s the best way to handle this? Do I need to switch to in-app purchases, or are there any workarounds? Any advice from someone who’s been through the process and has some ball knowledge would be appreciated.

Are you always searching for information about Lightsabers? Prices, technologies, dueling, cosplay or shelf queen collections? Sabersmith’s/ Installer’s/ Fabricators or Engraver’s?

Today I launched a Lightsaber DataBase.

Here's what a lightsaber database actually looks like when it's built for collectors.

Search by blade color. Filter by hilt material. Pull up soundboard specs in two taps.

Every vendor has a full profile - country, founding year, specialties, and what they're actually known for.

Every saber is tagged canon, Legends, original design, or custom.

No forum digging. No dead links. No asking the same question for the hundredth time.

This is Biker Jedi's DataBase - u/bikerjedi built it specifically for the high-end saber market.

Free. No login. Just go use it.

Have fun!

MTFBWY

https://preview.redd.it/o8ar2p962bbh1.png?width=1285&format=png&auto=webp&s=7a9535855c01b9929cabbd4e97b6b181e6c048f2

Clans - create and join clans. Engage on the Clan wall . Award Badges (work in progress) to your members

https://preview.redd.it/tygp7ndm2bbh1.png?width=1283&format=png&auto=webp&s=71b9174dfc417535ed5056385ad06e263e0e2ff8

Forums - discuss strategy or find others to group with or recruit for your clan with the forums threads. Off topic discussions for anything you want to just share with other gamers (like maybe GTA 6?)

WORKS IN PROGRESS

- Add friends as Sidekicks

- Badges fixes

- Synced Leaderboard with in game stats

let me know what you'd like to see!

(and yes we're still accepting games)

we're happy to be at this point and have to give a special shout out to all these creators who contributed their games to get this platform going:

u/macuseri1686 u/Birthday_Euphoric  u/Substantial-Bike-738 Doge-Man-2021 u/mayoti BeltwayBro Friendly_Fault_9753 Lettall BytekinShowdown v1dal Flat-Display-5989 u/SolvendraMMO PhotographNo725 OMGCluck SMB1172 u/demon5253 u/ninjaxan u/critical_ad_1325 u/Ok_Promotion_9578 u/bai13yd u/stinkskii u/metalheadindie u/iejenian u/Reckonerxy u/United-Case2691 u/radiantforce u/forThePeople707

These people are the REAL heroes 👏👏👏👏

Free Browser Games on SLAGDOCK | Play Now!

Hello!

Looking for some insight from people who have actually scaled apps built with Base44.

Once you've built and shipped an app, do you typically keep it hosted on Base44, or do you export the code and move to your own infrastructure?

If you migrate, what does your production stack actually look like?

Some questions I'm curious about:

• Where are you hosting? (VPS, cloud provider, Kubernetes, Docker, etc.)
• Are you using GitHub Actions or another CI/CD pipeline?
• Are you staying with Supabase, or moving to PostgreSQL, Neon, Firebase, PlanetScale, or something else?
• How are you handling authentication after migrating?
• What are you using for object/file storage?
• What does your monitoring stack look like? (Logs, metrics, uptime, alerts)
• How are you handling caching? Redis? CDN?
• Are you putting Cloudflare in front of everything?
• What's your backup and disaster recovery strategy?
• How are you managing secrets and environment variables?
• How are you handling email, queues, background jobs, and scheduled tasks?
• If you have AI features, what providers are you using and how are you managing API costs?

I'm especially interested in hearing from anyone running 10–30+ production apps or serving around 100k+ monthly users per app.

What does your infrastructure look like today? Roughly what are your monthly costs (hosting, database, storage, AI APIs, monitoring, CDN, etc.)?

Trying to understand where the point is that staying on Base44 becomes less economical than running your own infrastructure, and what a mature production architecture looks like once you've outgrown the platform.

Would love to see real-world architecture examples and cost breakdowns.

I paid the premium price because I wanted to use my domain name. It won't let me do that and it's asking for more money.

Hi, so as you many of you know now about my idea about an ERP system i am currently getting into more ideas which i want to implement but have difficulty to do so

So in my system there are photos along with text in which i would like to send it to the cutomer through a button onto his whatsapp. So i choose his number and then i click send which actually is pretty decent on the text version but i do face a problem on making the photos attached to the message and to be sent directly to him. if you have the solution for this kind of thing please let me know and how to implement that or what is needed actually to do so ?

I really like Base44, and I managed to build some great apps.
Two issues:
1 - Sometimes it's clear they "built" a bug when adding any new prompt. Why should I pay with tokens for bugs that are not my fault?
2 - I'm afraid when I'm trying to work with a large amount of data (10K records), it's a little bit beyond the base44 capabilites. Any idea what I can do? The entire process becomes really slow or even crashes (happens a few times). IS there any way to "take" my entire app into a more robust platform? Will Claude Code be better? Or Lovable?

Claude Fable 5 is not just “a smarter model.” For Base44 users, the biggest change is that it can handle larger, more ambiguous, more multi-step app-building tasks without needing as much hand-holding. That also means your prompting style needs to change.

Older models often needed very detailed, step-by-step instructions. Fable 5 does better when you give it the goal, the context, the boundaries, and the verification requirements — then let it work.

This guide covers how Base44 users should prompt Claude Fable 5, how to write better custom AI instructions, how to avoid overbuilding, and how to use it for debugging, app planning, security, mobile fixes, and long app-building sessions.

---

1. The Biggest Prompting Shift

With older AI models, Base44 users often had to say:

«“Create this page. Add this button. Connect this entity. Then make this modal. Then add this validation.”»

With Fable 5, you can usually give a higher-level instruction:

«“Build the full customer onboarding flow for this app. Use the existing entities where possible, create only the missing ones, protect private user data, and verify every button, form, and route before you finish.”»

Fable 5 is better at connecting the dots. That means your prompts should focus less on micromanaging every click and more on clearly defining:

- What you are building

- Who it is for

- What already exists

- What must not be changed

- What the finished result should include

- How the AI should verify the work

The better the context, the better the output.

---

2. The Base44 Prompt Formula

Use this structure for most Fable 5 prompts inside Base44:

I am building [type of app] in Base44 for [target user].

The goal of this task is to [specific outcome].

Current app context:

- Existing pages:

- Existing entities:

- Existing user roles:

- Current problem or missing feature:

Build or fix the following:

Rules:

- Do not remove or rename existing working features unless required.

- Reuse existing entities and components where possible.

- Do not create duplicate entities, duplicate pages, or duplicate workflows.

- Protect user-specific data with proper role and ownership logic.

- Do not overbuild beyond this request.

- If something is unclear but you can make a reasonable assumption, proceed and state the assumption at the end.

- Only stop and ask me if the task is blocked by information only I can provide.

Before finishing:

- Test every button, form, route, and workflow related to this task.

- Confirm what was changed.

- List anything that still needs my attention.

This gives Fable 5 enough structure without choking it with unnecessary detail.

---

3. The “Act When Ready” Instruction

Fable 5 can sometimes overthink, overplan, or give you a long strategy when you wanted it to build. Add this instruction when you want action:

When you have enough information to act, act. Do not keep re-explaining the plan. Do not re-litigate decisions already made. Make the best reasonable implementation choice and continue. Only pause if the work is blocked by missing information that only I can provide.

Use this especially when you are asking it to:

- Build a full feature

- Fix multiple bugs

- Review an app

- Clean up workflows

- Connect entities

- Repair broken logic

---

4. Prevent Fable 5 From Overbuilding

Because Fable 5 is more capable, it may try to “improve” things you did not ask it to touch. This can be dangerous in Base44 because one fix can accidentally change working pages, roles, entities, or workflows.

Use this instruction:

Do not add features, refactor unrelated areas, rename existing items, redesign pages, introduce new abstractions, or create duplicate systems unless the task specifically requires it. Do the simplest thing that solves the stated problem cleanly. Preserve existing working functionality.

This is very important for bug fixes.

Bad prompt:

Fix my dashboard.

Better prompt:

Fix the dashboard loading issue only. Do not redesign the dashboard, do not change unrelated widgets, and do not modify the existing entity structure unless the loading issue is directly caused by the entity setup.

---

5. Custom AI Instructions for Base44

Base44 users should create a strong custom instruction block for Fable 5. This helps the AI stay consistent across a long build.

Use this:

You are helping me build and maintain a Base44 application.

Primary behavior:

- Lead with implementation, not theory.

- When enough information exists to proceed, proceed.

- Ask questions only when the task is genuinely blocked.

- Preserve existing working functionality unless I specifically ask you to replace it.

- Do not create duplicate pages, duplicate entities, duplicate fields, or duplicate workflows.

- Reuse existing app structure whenever possible.

- Keep the app simple, maintainable, and production-minded.

Base44 rules:

- Treat entities as the app’s source of truth.

- Keep entity relationships clear and minimal.

- Protect private user data with proper ownership, roles, and access logic.

- Never expose admin-only data to normal users.

- Never weaken authentication, permissions, or role checks to make a feature easier.

- Do not create fake security. If something needs real access control, say so and implement it correctly.

- Do not assume public pages should have access to private entities.

- Do not remove RLS, role checks, or user ownership logic unless I explicitly ask and understand the risk.

Build behavior:

- For new features, build the full user flow, not just the UI.

- Include empty states, loading states, error states, and success feedback where relevant.

- Make sure buttons actually do something.

- Make sure forms save to the correct entity.

- Make sure list/detail pages pull from the correct data.

- Make sure dashboards show real connected data, not static placeholder data.

- Avoid placeholder logic unless I specifically ask for a demo.

Debugging behavior:

- Diagnose before changing.

- Identify the likely root cause.

- Fix only the affected area.

- After fixing, verify the related workflow.

- Report what changed and what still needs review.

Communication style:

- Be clear and direct.

- Start final responses with the outcome.

- Do not dump unnecessary theory.

- Do not use dense shorthand.

- Tell me what was built, what was fixed, what was changed, and what still needs attention.

---

6. Best Prompt for Building a New Base44 Feature

I am building a [type of app] in Base44.

I need you to build a complete [feature name] feature.

Purpose:

[Explain why the feature exists and who uses it.]

Users involved:

- Admin:

- Logged-in user:

- Public visitor:

- Other role:

Feature requirements:

Data requirements:

- Use existing entities if possible.

- Create new entities only if needed.

- Keep fields simple and clearly named.

- Connect records to the current user where ownership matters.

UI requirements:

- Build the main page.

- Add create/edit/delete actions where appropriate.

- Add loading, empty, error, and success states.

- Make the UI responsive.

Security requirements:

- Users should only see their own data unless they are admins.

- Admin-only actions must not be visible or usable by normal users.

- Do not expose private records publicly.

Before finishing:

- Verify the full workflow from start to finish.

- Confirm every button and form works.

- Tell me exactly what was added or changed.

---

7. Best Prompt for Fixing Bugs in Base44

I need you to debug this Base44 app issue.

Problem:

[Describe the bug.]

Expected behavior:

[What should happen.]

Actual behavior:

[What is happening.]

Relevant pages/components:

[List them if known.]

Relevant entities:

[List them if known.]

Rules:

- Diagnose the cause before making changes.

- Fix only the broken workflow.

- Do not redesign the page.

- Do not rename entities or fields unless absolutely required.

- Do not create duplicate logic.

- Preserve all working functionality.

- If multiple causes are possible, inspect the actual implementation and fix the confirmed issue.

After fixing:

- Test the workflow.

- Confirm the root cause.

- Explain what was changed in plain English.

---

8. Best Prompt for Cleaning Up a Messy Base44 App

Review this Base44 app for structure, duplication, broken flows, and maintainability.

Focus on:

- Duplicate pages

- Duplicate entities

- Unused fields

- Broken buttons

- Forms that do not save correctly

- Pages using placeholder data

- Role or permission issues

- Admin features exposed to normal users

- Workflows that are incomplete

- Confusing navigation

- Features that should be merged or simplified

Do not make changes yet.

Give me:

1. A clear summary of the current state.

2. The biggest problems.

3. What should be fixed first.

4. What can be safely removed.

5. What should not be touched.

6. A step-by-step cleanup plan.

This is important: when you only want an audit, tell Fable 5 not to make changes yet.

---

9. Best Prompt for Security and RLS Review

Perform a security and access-control review of this Base44 app.

Check for:

- Private user data exposed to other users

- Admin-only data exposed to normal users

- Public pages pulling private entity data

- Missing ownership checks

- Missing role checks

- Users able to edit or delete records they do not own

- Admin routes visible or accessible to non-admins

- Forms that allow unsafe data changes

- APIs or workflows that bypass intended permissions

Rules:

- Do not weaken security to make features work.

- Do not remove role checks.

- Do not make private data public.

- If something is insecure, explain the risk clearly.

- If you can safely fix it, fix it.

- If the fix requires a decision from me, explain the decision needed.

Final output:

- Critical issues

- High-priority issues

- Medium-priority issues

- What was fixed

- What still needs review

---

10. Best Prompt for Mobile App Export Problems

Base44 mobile exports can break when the app depends on native mobile features, app store payment rules, push notifications, deep linking, or permissions that the default wrapper does not handle well.

Use this prompt:

Review this Base44 app for mobile app readiness.

The goal is to prepare it for iOS and Android app store submission.

Check:

- Responsive layout problems

- Mobile navigation issues

- Buttons or forms that are hard to use on mobile

- Authentication flows

- Payment flows

- StoreKit or Google Play Billing requirements

- Push notification needs

- Deep linking needs

- File upload or camera permission needs

- External links

- App store rejection risks

- Features that need a native wrapper such as Capacitor

Do not assume the default Base44 mobile export is enough.

Give me:

1. What will work as-is.

2. What is likely to break.

3. What app store issues may come up.

4. What should be moved to native functionality.

5. What should be handled with Capacitor or another wrapper.

6. A prioritized fix plan.

---

11. Best Prompt for Long Build Sessions

Fable 5 is better at long, multi-step builds, but you still need to control how it reports progress.

Use this:

Work through this task end to end.

Before reporting progress, verify each claim against the actual work completed in this session. Do not say something is done unless it has been implemented or confirmed. If something failed, say it failed. If something was skipped, say it was skipped. If something needs my input, explain exactly what input is needed and why.

Do not end with a promise to continue. Continue until the task is complete or genuinely blocked.

This helps reduce fake “all done” summaries.

---

12. Best Prompt for App Planning

Fable 5 is very good at turning a rough app idea into a structured Base44 build plan.

Use this:

I want to build a Base44 app for [audience].

The app idea is:

[Describe the idea.]

Help me turn this into a build plan.

Give me:

1. The core app concept.

2. The user roles.

3. The main pages.

4. The required entities.

5. The key workflows.

6. The admin features.

7. The security and permission rules.

8. The MVP version.

9. The phase-two features.

10. A series of Base44 build prompts in the correct order.

Keep the MVP realistic. Do not overbuild the first version.

---

13. Best Prompt for Rebuilding an Existing App in Base44

I want to rebuild an existing app in Base44.

Current app:

[Describe the old app.]

Users:

[List user types.]

Core workflows:

[List workflows.]

Known problems:

[List problems.]

The goal is not to clone the old app exactly. The goal is to rebuild the useful business logic in a cleaner, modern Base44 structure.

Give me:

1. What the app does.

2. What features matter most.

3. What can be simplified.

4. What entities are needed.

5. What pages are needed.

6. What workflows are needed.

7. What permissions are needed.

8. What should be built first.

9. What should wait until later.

10. A prompt-by-prompt rebuild sequence for Base44.

---

14. Best Prompt for Reviewing Screenshots

Fable 5 is stronger with visual analysis, so screenshots can be very useful.

Use this:

Review these screenshots of my Base44 app.

Look for:

- UX problems

- Confusing layout

- Missing actions

- Broken visual hierarchy

- Mobile responsiveness concerns

- Trust issues

- Conversion problems

- Missing empty states

- Missing success/error feedback

- Anything that looks unfinished

Give me:

1. What is working.

2. What looks broken or confusing.

3. What should be improved first.

4. Specific Base44 prompts I can use to fix the issues.

---

15. Best Prompt for Making the App Client-Ready

Review this Base44 app as if it is being delivered to a paying client.

Check:

- Broken buttons

- Broken forms

- Placeholder data

- Missing loading states

- Missing empty states

- Missing error states

- Incomplete workflows

- Poor mobile responsiveness

- Admin access issues

- User data isolation

- Navigation problems

- Dashboard accuracy

- Client-facing polish

Give me:

1. Pass/fail status.

2. Client-readiness score from 0 to 100.

3. Critical blockers.

4. Important but non-blocking issues.

5. Nice-to-have improvements.

6. A launch cleanup prompt.

---

16. Memory System for Base44 Projects

Fable 5 works better when it can refer back to project decisions. For Base44 apps, create a simple “Project Memory” document.

Recommended sections:

# Project Memory

## App Name

## App Purpose

## Target Users

## User Roles

## Core Pages

## Core Entities

## Important Workflows

## Security Rules

## Design Rules

## Decisions Already Made

## Things Not To Change

## Known Bugs

## Future Features

## Client Preferences

## Prompt History

Then use this instruction:

Before making changes, review the Project Memory. Do not contradict decisions already recorded there unless I explicitly ask you to revise them. If you discover a new confirmed decision, add it to the Project Memory summary.

This is especially useful for large apps, client projects, and rebuilds.

---

17. What Not to Ask Fable 5 To Do

Avoid prompts like:

Think step by step and show me all your reasoning.

Instead, ask for:

Give me a concise explanation of your decision, the implementation approach, and any tradeoffs I need to know.

Do not ask it to expose hidden reasoning. Ask for conclusions, rationale, checks, and implementation notes.

Better:

Explain the root cause, the fix, and how you verified it.

---

18. The Best Base44 “Master Instruction” for Fable 5

Use this as your main reusable instruction:

You are my Base44 build partner.

Your job is to help me plan, build, debug, secure, and polish Base44 applications.

Work style:

- Be practical.

- Be direct.

- Build when enough information is available.

- Ask only when genuinely blocked.

- Do not over-explain simple tasks.

- Do not overbuild beyond the request.

- Do not create duplicate systems.

- Preserve working features.

- Verify your work before saying it is done.

Base44 standards:

- Every feature should connect UI, data, workflow, permissions, and user feedback.

- Every form should save correctly.

- Every button should have a purpose.

- Every page should have loading, empty, error, and success states where relevant.

- Every private record should be protected by role or ownership logic.

- Admin features must stay admin-only.

- Public pages must not expose private data.

- Dashboards should use real data, not placeholders.

When debugging:

- Diagnose first.

- Fix only the confirmed issue.

- Avoid unrelated refactors.

- Explain the root cause and the fix.

When planning:

- Keep the MVP realistic.

- Separate must-have features from later features.

- Recommend the simplest reliable Base44 structure.

When finishing:

- Start with the outcome.

- Then list what changed.

- Then list anything that still needs attention.

- Do not end with vague promises.

---

19. Simple Rule for Base44 Users

Bad Fable 5 prompting says:

«“Do this exact tiny thing, then this exact tiny thing, then this exact tiny thing.”»

Good Fable 5 prompting says:

«“Here is the goal, here is the app context, here are the boundaries, here is what good looks like, and here is how to verify it.”»

That is the real difference.

Fable 5 does not need more micromanagement. It needs better context, clearer constraints, and stronger verification instructions.

---

20. Final Takeaway

For Base44 users, Claude Fable 5 is best used as a senior build partner, not a basic prompt executor.

Use it for:

- Planning full apps

- Cleaning up messy builds

- Debugging broken workflows

- Reviewing security

- Preparing apps for clients

- Turning screenshots into improvement plans

- Creating rebuild strategies

- Writing prompt sequences

- Auditing mobile readiness

- Managing long app-building sessions

The key is to stop prompting like you are giving instructions to a junior assistant and start prompting like you are briefing a senior developer who understands product, structure, security, and delivery.

Give it context. Set boundaries. Require verification. Then let it work.

My biggest issue with Base44 has been that I am always able to create production ready web apps, however going to the app store is my biggest point of friction, and with my first app, I ended up having to hire someone to do it for me. I imagine lots of people are also finding a similar problem.

To help, I've been spending the past few months building a website that does this for you, with minimal friction. It is a webview wrapper right now (native features coming soon) however the simplicity that it gives you, being able to so easily go from website to iOS, is what really makes it something I'm proud of.

I just thought I'd share it here, because I imagine a lot of vibe coders are experiencing a similar issue right now.

Hi. I've been using base44 for 4 months with my language students. Well, I like the experience, and so do they. But what bothers me and my students is the fact that sometimes the app won't open the data. It's like we have been logged out, the app says "log in to see the content", or "no content found" (messages that appear in case that's real, but it's not) so we need to reload the page in order to make it work. Well, that's not a biiig problem itself if it happens once in a while, the big problem is that it happens many times!!! So in one class, my student and I have to keep reloading the pages many times, and it's become a "something". The app I created is good, but this issue is taking out all of its value. I've already tried basically everything, asked help to Claude, tried to figure out the problem myself and make some changes... all in vain. Nothing has changed and I'm getting annoyed with that. Damn...

https://khalilplaysx.base44.app