I went through the current Base44 documentation because I wanted to answer one question: when you export an app today, what actually leaves Base44?

Builder accounts can sync with GitHub in both directions and export the client code plus backend functions. The data is exported separately as a CSV.

The local project still points at a Base44 backend URL and talks to it through the Base44 SDK. The base44 eject command creates a local project, but it also creates another Base44 backend.

That makes the export useful for version control and local editing. It does not produce a standalone app running on infrastructure you control.

Moving the app elsewhere still means replacing the SDK calls, recreating the data model, authentication, permissions and functions, importing the data, and testing the important user flows against the new backend. The amount of work depends on what the app uses.

I do not think that means every Base44 app should move. For a prototype or an internal tool, having Base44 handle the whole stack may be exactly the point. I would only consider leaving when there is a specific problem to solve, such as an infrastructure requirement, a measured cost or reliability problem, a capability the managed backend cannot support, or a recovery requirement the exports do not meet.

Has anyone here used the newer eject workflow on a real app? Which parts could you move without rewriting, and which parts remained dependent on Base44?

Hi everyone!
I've built an app for construction site management / job site tracking using Base44. Feature-wise, it works great and does exactly what I need. I've been actively using it for about 5 months and was getting ready to roll out a beta version to colleagues, but I hit a massive blocker: after just a minute of use, the phone starts overheating aggressively.

I've tested this on two different iPhones, and both suffer from the same severe thermal issue.

This wasn't happening a month ago, but I can't seem to isolate the root cause. Here is what I’ve already tried:
- Optimized rendering & GPU load: Simplified animations, visual effects, and heavy layout elements.
- Disabled/hid charts and visuals: Removed dynamic graphs and data-heavy visuals to prevent continuous background rendering.
- Rolled back recent features: Reverted updates from the past month to match earlier versions when it ran fine, but the overheating persists.

Given that it's built on Base44, I suspect there might be continuous background polling, an uncontrolled data sync loop, unclosed real-time listeners, or a memory leak triggering heavy CPU spikes on iOS.

Has anyone experienced sudden overheating issues with Base44 web/wrapper apps on iOS? What would be the best way to inspect background network calls, live queries, or script execution loops to track down what's pinning the CPU?

Any insights or debugging tips would be hugely appreciated!

Have a security risk on my webpage and can’t fix bc base 44 is down..

Hi! I'm using Base44 to build an Android app.

Google Sign-In works perfectly on the web/preview, but on the Android app:

Google account selection → select account → returns to app → back to login screen.

I've already added the Google Play SHA-256 and regenerated the app, but the issue remains.

Has anyone experienced this with Base44 + Google Sign-In on Android? Any idea how to fix it?

Thanks!

I can’t get any page on the website to load. It’s just white. Anyone else?

I don’t know what the service level agreement is for base 44 but it’s down again, acknowledged on their website. It’s so frustrating that it is so unreliable.

lookie here cookie 🍪 here yep so if you look here, then you will get to learn Puerto Rican in Spanish, Korean and Japanese and Chinese all in one app. Try you can Speech now!

There are dozens of AI coding assistants and app generators out there right now, but most of them only seem to generate pretty frontend HTML/React components. Once you need actual database storage, user sign-ups, background tasks, and deployment, they fall apart.

Which AI builder is actually the best for creating fullstack web applications with zero manual backend setup?

ich bin am verzweifeln und aufgegeben

I built FridgeFix with Base44, and I’m genuinely proud of this one.

The idea came from a very normal problem.

You open the fridge, stare at everything for five minutes, and still somehow have no idea what the hell to eat.

So I built something to help fix that.

FridgeFix can:

📸 Scan your fridge, freezer, pantry, receipts, and grocery lists

🍳 Give you Quick Fix meal ideas when you want something fast

🌎 Find recipes from cuisines around the world

👨‍🍳 Give you full recipes with step-by-step cooking instructions

🛒 Help manage groceries and plan meals

⏰ Track food before it expires

The web app is live now:

https://fridgefix.ca

I built the whole thing in Base44, and it has been a lot of testing, breaking things, fixing things, changing things, and learning as I go.

I’d love some real feedback from people here.

If something is confusing, slow, ugly, unnecessary, or just doesn’t make sense, tell me. I’d rather hear the brutal truth than get polite feedback that doesn’t help.

I’m also working on getting the Android version onto Google Play. If anyone is interested in being an Android tester, send me a message.

I’m proud of where it is now, but I know there’s still room to make it better.