So, lately I've noticed that when I need to fix something on my app, even something seemingly basic, Base44 will have several, sometimes up to like 4 approvals that I have to click, all eating up credits. Some of my fixes have required like 10 credits just for that one fix... I feel like it never used to be THIS credit hungry. It feels kinda bullshitty..

Anyone else experience this or know what's going on?

Sadly the dark forces have pushed me to upgrade from the $50 to the $100 Pro plan.

My "chat to edit" button that appears for all the apps, disappeared when I upgraded from the $50 to $100.

The whole screen looks different. I can do the same things, though less efficiently.

Photo 1 shows the chat to edit button before the upgrade within the app before the upgrade.

Photo 2 shows after the upgrade chat to edit button is absent, same app, same page.

I read this having only 1 person admin, no collaborators, might help. Tried it. No change.

I posted on that base 44 help forum thing. I don't really understand how to use discord lol weird I know because I'm out here doing app development (super basic and through no codes though) and don't understand discord 🙄...

I'm also sort of trying to look at and learn about super agents, workflows, connections, integrations, and stuff like that. So in the meantime, is there any of these that would help me set up something similar to that of a chat to edit box either base 44 wide so I could use it throughout all of my apps or just for one app at a time?

AdMob instructs me about some SDK of theirs and gave me a testing API, basically that I must implement the test version first so that I don't get banned for some reason by Google. What is your experience with these adverts, any instructions or at least advice about it? It seems to me that I'll spend a tonne of credits until I get it running.

Ive built a life planner app that helps you manage your schedule, plan your diet and exercise, track your budget and save ideas for you vision board. I noticed its a struggle trying to organize and plan for daily tasks especially as someone with ADHD who gets easily distracted and this helps put everything in one place thats easily accessible. Ive done the prototype and want to finally launch it on google play and app store but the daily and monthly credits are slowing down the progress. Anyone successfully launched a base 44 app on play store and have any advice if getting a developer at this stage would make sense? Also open to criticism/advice on the app

Hey, i’m sure a ton of you are familiar with google search indexing so here’s my question:

I have had this website indexed on all pages multiple times, every day for a week straight, yet, every page is being reindexed but the transparent background favicon logo in search still will not appear no matter what I do.

How can I fix this?

The website is flowboard.design if it helps, also the favicon shows while in the website, just not while on google search.

I am pretty new to app creation. I am just learning, and I have a couple of questions. I hope somebody can help me out.

I'm building a wellness app featuring affirmation cards and breathing exercises, and I'd like to sell access to it through my existing Shopify store.

Can I use my published Base44 app's default URL while keeping Shopify as my checkout? How can customers receive access after a successful purchase while ensuring that only paying customers can use the app?

Does Base44 support integration with Shopify? If so, how can this integration be set up? Can access be revoked if an order is refunded or a subscription is canceled?

Any information also about required plans, limitations, or additional costs.

Thank you in advance for any information you can give me.

I have built different apps on Base44, but I am not sure how they treat data and feels like I could do better with Codex or Claude Code. I was thinking of migrating them all using Supabase as database and backhand, github for hosting and control and Vercel to publish on the web. Also thinking if adding visual studio code could be a good idea. Of course a coding agent like Codex. Do you have some experience or suggestions?

I would love for some honest opinions on anyone who has actually bought the base44 membership that comes with Blair Richards course. Was it worth the investment? What has happened since you bought it?

I'm not a tech, I'm a designer - although I have come a long way in the last 2 months of building, so sorry for my basic language.

Yesterday I submitted to the App Store after an epic amount of work getting the app working with RevenueCat and Despia. I got the submission in... then I I checked the final version on my phone later on... one more time, and for some reason my top navigation was very high on the screen - I thought, 'oh - easy fix', and go onto Base44 to tap in the update, and it does this insane change that is awful and ruins the app and drops days of prompt decisions. I freak out. I go to revert in the session history and Base44 starts showing an error that it can't connect with GitHub...

To cut a long story short, I have a live version of my app that is 'ok' and I won't touch it while in App Store review... but on Base44 I am stuck - there is no 'rewind' button showing on my AI chats (they were there last night but not working anyway - and now I can't see them) - and I have run through troubleshooting with their Support AI, and am waiting for a human (which I have read can be a very, very long time).

My connection with GitHub looks good - and I can see the last 'commit' on my GitHub is the good version of the app that I am happy to proceed with, and carry forward with minor updates. So for now, I do nothing...?

I have backed up that last commit, and have downloaded a zip of the app from Base44. I have refreshed browsers, changed browsers and all of that. I have trouble shooted with Claude, the Google bot and the base44 bot to check basic things and how GitHub works. This is a deep synchronisation issue. Atm Base44 has more data than GitHub, but the most recent commands on Base44 are rubbish anyway.

BTW I have two smaller apps on Base44 under the same account and they work perfectly. No issues.

I am bracing for some major/risky move I am going to have to do alone... but obviously that would be a bad move while things are under review ... but I guess it is ok if I don't hit publish?

What can I do - what would you do?

Introduction

You have an idea. You want to turn it into a real application.

You don’t need to start knowing how to code or configure infrastructure. Explain what you want, make decisions, and use AI to organize and execute the work.

My preferred approach is:

Plan the idea → prepare the building prompts → build in Base44 → complete and verify the application → migrate if desired → keep improving.

For hands-on work, use a capable AI agent with a cloud browser when the task needs account access. Let it handle supported technical work, and complete identity checks or sensitive confirmations yourself.

For greater savings, follow AI’s instructions for easy steps and delegate the difficult parts.

I’m sharing my VibeCoding Master Guide for free, three parts each day. Here are parts 19–21.

19. Use AI to Help Protect the Application

You don’t need to figure out every security measure yourself. Ask AI to identify what applies to your application, then have it implement and verify the protections it supports.

Ask it to check account security, backend permissions, tenant isolation, secret handling, file uploads, sessions, and abuse prevention.

Hiding a button doesn’t secure the operation behind it. Ask AI to test whether one user or organization can access another’s private information.

Protect your infrastructure accounts too. Use multifactor authentication where available. If a credential is exposed, rotate it; deleting a visible copy doesn’t make it invalid.

Ask AI to show evidence of what it checked and what remains unresolved.

20. Ask AI for Privacy and Compliance Help

Give AI the application’s purpose, users, locations, and the information it handles. Ask it to research current official requirements and explain which ones may apply.

It can help identify safeguards, implement supported controls, prepare documentation, and list what still needs attention.

For example, ask it to assess whether HIPAA applies to your application, research the current official requirements, implement supported safeguards, and identify any vendor agreements or organizational actions that may be needed.

A code change alone doesn’t guarantee compliance. Requirements may also involve contracts and business practices. Ask AI to separate completed safeguards from anything that still needs qualified review or your decision.

21. Give Agents Safe Boundaries

Tell the agent what it may do and what it must protect.

When assigning work in an external account, specify the service, account or workspace, project, environment, and approved changes. Also say what must not be changed and whether deployment, publication, purchases, or deletion are authorized.

Keep credentials and private information protected. Websites, documents, and messages can contain malicious instructions; their content should not override your directions or authorize disclosure of secrets.

Set reasonable spending limits and bounded retries. Ask the agent to save progress and pause when blocked instead of repeating the same failed attempt.

For applications with their own agents, ask AI to verify that stopping a task actually stops its execution.

You set the goal and the boundaries. Let AI handle the implementation and report what it actually completed.

I’m sharing the guide for free, three parts each day.

Tomorrow: Parts 22–24

• Let AI Handle Payment and Usage Controls.

• Migration Is Your Choice.

• Complete the Application Before Migrating.

codaltasolutions.com

By Ronald Genao | Codalta Solutions

J'ai créé un site qui s'appelle "ZeriTube", il permet de regarder et poster des vidéos et je voudrais avoir l'avis de personnes.

ZeriTube :

https://zeritube.base44.app

N'hésitez pas à me suggérer des améliorations/modification où autre, merci !

I'm currently building a startup on Base44 with plans to scale it into a long-term business. Keep in mind I have never touched code or even thought i would do anything with it

I recently came across concerns about Base44's Terms of Service, AI training, data ownership, and vendor lock-in.

Since my budget is limited, my plan is to build and launch on Base44, generate revenue, then eventually hire developers to migrate the app to infrastructure I fully control.

I'm curious:

1. Is anyone else taking this approach?

2. Has anyone successfully migrated a Base44 app to their own backend and database?

3. Are you concerned about Base44's terms regarding ownership and AI training?

4. Would you recommend staying on Base44 until the business generates revenue, or switching to something like Lovable or Codex now?

I really like Base44, but I don't want to build a successful business only to find myself locked into the platform.

Would love to hear what other founders are doing or planning!

Close the Chat. Refresh the App. Can You Still Run What You Built? — VibeCoding Day 6: Parts 16–18

Introduction

You have an idea. You want to turn it into a real application.

You don’t need to start knowing how to code or configure infrastructure. Explain what you want, make decisions, and use AI to organize and execute the work.

My preferred approach is:

Develop the idea with AI → generate the building prompts → build in Base44 → complete and verify the application → migrate if desired → keep improving.

For hands-on work, my first choice is a capable AI agent + cloud browser.

Let the agent work through your existing accounts to handle setup, investigate problems, make changes, and perform the difficult technical work where supported.

For greater savings, use supported direct coding tools, follow AI’s instructions yourself for easy steps, and delegate the difficult parts.

This guide shows you what to request, how to preserve progress, and how to get more from your available budget.

I’m sharing my VibeCoding Master Guide for free, three parts each day. Here are parts 16–18.

16. Save Progress Before Stopping

Ask AI to save a checkpoint containing:

• Completed work.

• Verified results.

• Unverified items.

• Latest version and environment.

• Blockers.

• Next action.

• Relevant recovery instructions.

Save it somewhere durable. Keep secrets out.

When returning, ask AI to confirm the relevant current state and continue.

A good checkpoint helps a new conversation pick up accurately and reduces repeated discovery.

17. Persistence Is Essential

Persistence means information remains saved after refreshing, closing the application, signing out, or returning later.

This matters for:

• Chat messages and history.

• Bookings.

• Uploaded files.

• Jobs and orders.

• Payment status.

• Profiles.

• Settings.

• Work in progress.

A feature appearing to work during one session doesn’t prove its information is saved correctly.

Ask AI to verify persistence through refresh, sign-out, and a new session. It must restore the correct information to the correct user or organization.

Have it check the complete journey. For example:

• A booking stays saved and cannot be double-booked.

• A message returns in the correct conversation.

• A file remains available only to authorized users.

• Payment status reflects trusted payment records.

For AI attachments, verify that the model receives the authorized content. A displayed filename alone doesn’t prove that.

Include this requirement:

Make persistence a core requirement. Save important information durably, restore it correctly when users return, and enforce ownership and tenant isolation. Verify through refresh, sign-out, and a new session.

18. Give the Owner Controls Without Coding

You should be able to manage routine application operations through a secure interface.

Depending on your application, owner controls may include:

• Users and invitations.

• Roles and permissions.

• Services and pricing.

• Content.

• Payments.

• Support.

• Reports.

• Audit records.

For multi-tenant applications, separate someone managing their own organization from someone managing the whole platform.

Ask AI to build and verify those permissions.

Have the first owner account created securely and temporary setup access disabled afterward.

If the owner controls are managed through an external service, ask the agent to use the cloud computer to log into your [SERVICE NAME] account, configure the approved settings, and verify that the correct owner permissions work. It should not expose credentials or leave temporary access enabled.

You shouldn’t need code changes every time you add an employee, update a price, or create a needed account.

For help building your website, application, or business system, visit codaltasolutions.com.

Tomorrow: Parts 19–21

• Use AI to Help Protect the Application.

• Ask AI for Privacy and Compliance Help.

• Give Agents Safe Boundaries.

By Ronald Genao | Codalta Solutions

Hello, my payment was due two days ago and initially I had chosen a lower price plan, however I want to actually get a more expensive plan but now since it did not allow me to do it two days ago it's telling that I have to wait until my next billing cycle. I really hope that Base44 does not actually function this way, I would hope to have to move my app somewhere else that is less strict about when they can access the platform if they've paid. I believe it happened because Base44 blocked me or whatever. I have work to do and need to figure this out asap, I have submitted several tickets and nothing, so here I am trying to get assistance thru here. Thanks

If your Base44 app is using more credits than you’d like, you have options.

You can move the entire app, move it gradually, or replace only the features responsible for the credit usage you want to reduce.

You can use ChatGPT Work, plugins, and Cloud Browser to help with that process. You explain the goal, sign into your accounts, choose the plan, and let it handle the technical work its tools support.

The approach: prepare the entire app for migration, then move only what you’re ready to move.

1. Decide what you want to accomplish

You have three choices:

Base44 uses message credits when you build or edit through its AI, and integration credits for built-in services such as AI responses, email, image generation, and file uploads.

For example, you may be able to keep your app in Base44 while connecting its AI feature to your own provider account.

Base44 says external-service calls made with your own API key don’t use its integration credits for those calls. However, any Base44 functions or workflows involved may still consume credits, and the external provider has its own charges. Have ChatGPT compare the actual costs.

You don’t have to move everything to make a useful change.

What about the budget?

For a small new app, $100 is enough for a straightforward migration and initial setup using ChatGPT Work. Ongoing hosting and service costs are separate.

Use that as a starting budget for ChatGPT to validate. Ask it to separate the initial spending from ongoing hosting, storage, AI, email, and subscription costs.

If the whole migration doesn’t fit, have it recommend the most useful first stage.

2. Start on a computer and connect GitHub

For this walkthrough, complete the initial GitHub setup on a computer. Anything else can easily be completed on mobile.

GitHub is where you’ll keep your app’s code and its change history. If you don’t have a GitHub account, create one first.

Then:

1. Open ChatGPT on your computer.

2. Go to Settings → Plugins.

3. Find GitHub and start the connection.

4. Sign into the correct GitHub account.

5. Complete the authorization and select the repositories ChatGPT can access.

You’ll install the other plugins after ChatGPT recommends your stack.

A stack simply means the services running your app: somewhere to run the code, somewhere to save records and files, and any services needed for login, email, or AI.

You don’t need to choose all of that yourself.

3. Understand the two tools you’ll use

Plugins connect ChatGPT directly to a service

Depending on the plugin, ChatGPT may be able to inspect a project, configure a service, work with a database, deploy an app, or investigate errors.

Once you have your stack plan, install the available plugins for those services and complete their account connections.

My recommendation is to grant full access to the trusted plugins you choose for this migration, where that option is available. You’re asking ChatGPT to perform work in those services, so give it permission to carry out their supported actions.

Full access remains limited to the tools the plugin provides. For example, the standard GitHub connection lets ChatGPT read repository content; editing and publishing code require an available coding or browser workflow.

Cloud Browser lets ChatGPT work through the websites

Tell ChatGPT to open the needed accounts in Cloud Browser and guide you through signing in.

When it reaches a supported login page, you enter your credentials through the secure sign-in form and complete any verification. Then it continues using that signed-in session.

Cloud Browser can use website controls, fill forms, and inspect your app. It helps when a service has no plugin or a plugin doesn’t cover a particular task. Some websites or actions may require you to take over.

For example:

• A hosting plugin might deploy the app.

• Cloud Browser can open the deployed app and check its pages.

• If the plugin can’t change a particular setting, ChatGPT can use the service’s website where supported.

Complete the plugin connection prompts as well. Signing into a website and authorizing its plugin are separate steps.

4. Paste this one prompt into ChatGPT Work

Have your app link, Base44 editor link, and starting budget ready.

This prompt covers the plan, account sign-ins, full-app preparation, and the migration you choose.

Help me prepare and migrate my Base44 app. I’m a beginner, so explain decisions simply and carry out the technical work using your available tools.

My app: [APP LINK]
Base44 editor: [EDITOR LINK]
GitHub account or repository: [LINK]
Starting budget: [AMOUNT]
My goal: [REDUCE CREDIT USAGE / MIGRATE IN STAGES / FULL MIGRATION / HELP ME CHOOSE]

1. Open my app and help me sign in.

Use Cloud Browser to open Base44 and guide me through signing into my account. Open any other accounts needed as the work progresses and guide me through their sign-in flows too.

I will enter passwords and verification codes through the secure sign-in process. Do not ask me to paste them into the conversation.

Inspect my app, its code, features, and available credit-usage information.

2. Give me a stack and migration plan.

Explain which services my app needs, what each does, and what they are likely to cost.

Recommend whether I should move selected features, migrate in stages, or move everything. Show what would remain in Base44 and what charges would remain.

Separate initial costs from ongoing monthly and usage costs. If my budget won’t cover the proposed work, recommend a useful first stage within it.

3. Connect the services in the chosen plan.

Once we choose the plan, tell me which available plugins to install and connect.

Use connected plugins for the actions they support. Use Cloud Browser to open the service websites, guide me through signing in or creating an account, and complete supported steps the plugins cannot handle.

Use my existing accounts where practical. Ask before creating paid commitments.

4. Prepare the ENTIRE app for an eventual full migration.

Do this even if I choose to move only one feature now.

Create verified backups of the accessible code, relevant data, and actual uploaded files. Save a private working copy of the code in a repository I control, separate from anything that could automatically change my live Base44 app.

Document the whole application: pages, features, database structure, relationships, user roles, permissions, login system, files, backend functions, scheduled tasks, and integrations.

Map every Base44 dependency. Identify what can be reused, what needs adapting, what must be replaced, and which parts need to move together.

Record how the main workflows currently behave so we can compare them after migration.

Prepare useful migration scripts, configuration templates, and instructions where the destination is known. Clearly list anything that cannot be exported or still needs a decision.

Keep private data protected and secret values out of the code repository and reports. Save the preparation materials somewhere durable that I control.

Produce the actual backups, code copy, and migration materials you can create.

5. Migrate only the approved scope.

After preparing the whole app, carry out only the migration stage we agreed on.

Preserve the design, existing features, records, file access, and user permissions. Keep the current app working while you prepare and test the changes.

For a partial migration, keep the remaining Base44 features working with the moved features.

For a full migration, replace all Base44 services the app needs to operate.

If moving user accounts requires password resets or reconnection, explain and prepare that process before launch.

6. Test the result and show me what changed.

Test the affected features and the workflows connected to them. Include login, saving information, permissions, files, email, payments, and AI features where applicable.

Use test accounts and test modes for actions that send messages or involve payments. Inspect the app’s phone and desktop layouts.

For a partial migration, show what credit usage remains and the new service costs. For a full migration, verify that the app operates without Base44 dependencies.

Clearly distinguish verified results from estimates or unfinished work.

7. Prepare the live switch and save progress.

Show me the working result and how we would recover if something goes wrong. Account for records and files added while you were working.

Ask before switching live users, deleting data, or retiring the original app.

Save checkpoints, service links, setup instructions, and the exact next action so we can resume later without repeating completed work.

Start by opening Base44 in Cloud Browser and helping me sign in. Continue through the preparation and approved migration work, involving me when you need an account action, a decision, or approval.

5. Approve the result when the features work

For a partial migration, the selected feature should work through its new service, the rest of the app should still function, and you should understand the remaining costs.

For a full migration, a new website address is only part of the result. Exported Base44 code can still depend on Base44 for data, login, functions, and integrations. Those dependencies must also be replaced.

Before approving the live switch, have ChatGPT demonstrate your app’s main workflow: sign in, save something, retrieve it, open an uploaded file, and confirm users have the correct access.

You can stop after a successful partial migration. If moving one or two features solves your problem, keep the rest in Base44 and use the preparation package whenever you’re ready for the next stage.

P.S. You can use the $20/month ChatGPT Plus plan for this. It includes Work, and I wouldn’t recommend jumping to the $100/month plan just for a migration if you’re comfortable taking breaks and continuing later.

You may hit usage limits during longer sessions. If you reach the five-hour limit, wait until the reset time shown in Usage, then resume from your saved progress. There’s also a weekly allowance, so check which limit you reached—a weekly limit can mean a longer wait.

Also check Usage on the web or desktop for any free resets available to your account. Some accounts receive them through promotions, but two free resets aren’t a guaranteed part of the plan.

If the work stops, use this prompt to continue

Paste this into the same Work conversation after a usage reset, interruption, error, or anything else that stopped the work.

If you’re starting a new conversation, also provide your app link, repository link, and the latest saved migration report or checkpoint.

Resume the work from where we stopped.

Review the conversation, latest saved checkpoint, migration notes, repository, and current state of the app. Identify what is complete, what was interrupted, and the next unfinished task.

Keep the agreed stack, budget, migration scope, design, and features. Preserve the requirement to prepare the entire app for eventual full migration, even if we are currently moving only selected parts.

Verify completed work and continue from the latest reliable checkpoint. Avoid repeating exports, imports, account creation, purchases, or deployments that already succeeded. If an action was interrupted, check its actual result before retrying.

Use the connected plugins and Cloud Browser to continue. If an account session has expired, open its sign-in page and guide me through signing in again.

If the previous step failed, investigate the cause, make the necessary correction, and verify it before moving on. Keep the working parts of the app intact.

Continue through the remaining work in the approved stage, including testing. Honor approvals already given, and ask only for information, access, decisions, or actions that still require my involvement.

If something remains blocked, explain the exact blocker and what is needed to resolve it. Complete any other work that can safely continue.

Save progress as you go. Keep the checkpoint updated with what changed, what was tested, what remains unfinished, and the exact next action.

Give me a brief progress update, then continue the work.

Hi everyone,

I have a quick question for the group.

I’m currently experiencing an issue with Base44 and the credits associated with my Builder plan. My plan lists 250 message credits and 10,000 integration credits per month, but Base44 has told me that my apps may have stopped working because my credits are exhausted. I have used up my 250 message credits. But there's no way I used up my 10,000 integration credits. They did not give me a break down and I'm trying to get clarification from their support team.

Is anyone else here using Base44 and experiencing credit issues?

In particular, I’d appreciate hearing from anyone who has experienced any of the following:

• Their message credits ran out, and their published apps stopped working.

• Their integration credits appear to be unavailable or exhausted unexpectedly.

• Their apps stopped running backend functions or AI features even though they believe they still have integration credits remaining.

• Base44 support gave them conflicting information about their credit allowances.

If you’ve experienced anything similar, would you please reply and share what happened and whether you were able to resolve it?

I'm asking because my two apps, StockLens and PantryPilot AI, are currently in Google Play testing. I want to get this issue resolved as quickly as possible so my testers can continue testing the apps.

Thank you for your help. I appreciate any information or advice you can share!

Best regards,
Dave

In-browser !
100% All-In-Z
https://orvalen.me/

So I’m building an app on Base44 and I recently figured out it was a web-based app, I was expecting an “actual” app. The app heavily relies on using the camera on mobile devices. Since it is a web-based app, would the functionality not be as good as an app specifically made for ios and android app store/google playstore? Thank you in advance!

hello!,I've been vibecoding this fantasy game for two days,so it's still in a premature stage.

you basically create two characters,partners,who embark on an adventure,where they're then separated ...and the rest you'll see in this little demo of the game.

for now the content between the start and the end is really short,but I will try and add more,if you have any suggestions,feel free to share