When submitting to the Apple app store, App Store Connect requires multiple logins. These can be enabled from the Base 44 App Dashboard to allow users to sign in with Apple. This works on the URL. However, it does not work in ios. Apple Sign In in the native WKWebView environment requires native SDK support, which is not yet available in Base44's current wrapper. So essentially - apps created in Base 44 are blocked from being published on the app store when submitted to Apple. I really how Base 44 can prioritize this new feature. I was hoping to publish my app.

Joe Gallagher 40 minutes ago

💡

Feature Request

I’ve been having difficulty changing the date directly in the database. This is a known time zone issue — the date field stores 2026-03-11, but the Base44 editor interprets it as UTC and displays March 10th (the previous day) due to the Brazilian time zone offset (UTC-3). Unfortunately, this records editor is native to the Base44 platform (the backoffice/dashboard panel) — it’s not something I can modify through the app’s code. This behavior occurs because the format: "date" field is internally treated by the editor as a UTC datetime. What I can confirm is that the data in the database is correct (2026-03-11). The display as "March 10th" is just a visual bug in the platform’s editor. Options: Ignore the visual discrepancy in the editor — the actual data is correct, and your app displays it properly. Report the bug to Base44 support so they can fix the records editor. If you need to edit dates frequently, I can create an editing screen within your app where dates will display correctly in pt-BR. Finally, could you please let me know if there is any possibility of implementing an improvement on the Base44 platform to handle date fields without this time zone issue?

Financeiro InMediam about 2 hours ago

💡

Feature Request

Would be great have the possibility to personlize the invitation email

Manuel Catena about 4 hours ago

💡

Feature Request

I suggest offering new subscribers an incentive during the onboarding period: if a user uses up all their monthly credits before the end of the month, grant them an additional 50% of their subscription credits—for the first three months. During the launch period, users need flexibility the most, and an incentive like this can make a big difference in their experience.

Music Lab about 7 hours ago

💡

Feature Request

אני מבקש להוסיף אפשרות לרכישת קרדיטים חד-פעמית, מחוץ למנוי הרגיל. לפעמים משתמש מסיים את הקרדיטים שלו באמצע החודש ואין לו צורך בשדרוג לפלאן יקר יותר לטווח ארוך – רק נקודתית. אפשרות כזו תיתן גמישות ותשפר משמעותית את חוויית המשתמש

Music Lab about 7 hours ago

💡

Feature Request

The problem I have with the Base44 email sent to the user is just that - its not my email. If I could amend the identification aspects on the email and add a short message from me, the whole thing would be fine. I am building a relationship with a client and in the process the client gets an email with identification of sender that is not recognised. I don’t want to change or circumvent the security aspects of the platform. I just want that which is sent by my business to my clients to be properly identified as coming from me and not a third party who is unknown to my client. I want all communication from me my client to be clearly identified and I want the message it contains to be my message in my style and my voice. What’s wrong with that? Please allow me to change the sender identification and the massage on my emails. That’s all I ask.

Colin Cox about 12 hours ago

💡

Feature Request

I build backend management systems into my apps for clientele lead generation- quotes- invoice etc. this all link to home page. I want to be able to publish these backend employee only functions to a mobile (Apple or google play) app only and bypass customer facing portal.

Michaella Cooke about 15 hours ago

💡

Feature Request

HIPAA is an absolute must. This isn’t just a huge win for your clientelle, you are leaving so much money on the table by not implementing this. Please upvote. This should have been number one priority on the list as of yesterday.

Jeff Whisenant about 16 hours ago

💡

Feature Request

My entire app is gone. I spent a lot of time making it and I paid for the builder subscription. Also, I did not realize that I was paying for an entire year. The language made it sound like I was upgrading for a month and paying the difference but my credit card was hit with 460 dollars. The confirmation email I received stated that i moved to the builder subscription for 20 dollars a month. I would like a refund as my entire app is deleted anyway.

Kiley McMahon about 16 hours ago

💡

Feature Request

I'm currently on the Builder plan and consistently run out of credits well before my monthly reset date. The only option available is to upgrade to a more expensive plan tier, which feels like an unnecessary and costly workaround for what should be a simple issue. What makes this more frustrating is that I’ve already paid for lower-tier subscriptions twice, only to run into the exact same limitation each time — exhausting credits early with no flexible way to continue without upgrading entirely. That experience makes the system feel restrictive rather than scalable. Why this matters: I'm paying for a full billing period but unable to use the service for the entire duration once credits run out Being forced into higher plans just to continue working creates avoidable cost pressure It gives the impression of being “locked out” mid-cycle unless I spend more Many SaaS platforms offer flexible credit top-ups or add-ons without forcing a full plan upgrade What I’m requesting: A credit top-up option — allow users to purchase additional credits mid-cycle at a fair rate Or credit rollover — unused credits carry forward to the next billing cycle These options would make the platform feel far more user-friendly and sustainable for active builders. I genuinely enjoy building on Base44 and want to keep using it long-term, but the current credit model makes that difficult to justify. A more flexible system would go a long way in improving user retention and overall experience.

Ogaolopa about 19 hours ago

💡

Feature Request

You need to create a few features other with the ability to turn on and off. The ability to customize the subject line for the verification email, instead of using just the app name. Ability to resend verification email. Ability to send verification to sms or mms. Ability to send a verification link other than just the code.

salvosports about 19 hours ago

💡

Feature Request

Thanks for reaching out. I can see you're looking to have some Android manifest flags updated in your mobile app build — specifically things like android:resizeableActivity="true" , removing the screenOrientation lock, and updating to the new WindowInsets edge-to-edge API. I want to be transparent with you: these are platform-level build configurations that are part of how Base44 generates the native wrapper for your app. Unfortunately, these aren't settings that can be customized on a per-app basis through the dashboard or AI chat — and they're also not something I'm able to modify directly from support.

New OKC about 20 hours ago

1

💡

Feature Request

Não poder mudar a linguagem dos emails recebidos aos usuários de inglês para português e não poder incluir o CPF para login é péssimo. Vou migrar de plataforma, infelizmente.

Jessica Monteiro Bueno about 20 hours ago

💡

Feature Request

Can I request new connectors for the platform? For app users. Specifically: Google Search Console — for SEO keyword rankings and click data X/Twitter — for post analytics (impressions, engagements, clicks)

Leon Stern about 22 hours ago

💡

Feature Request

I have a domain name hosted by BASE 44 for the app; this is needed for Google Play Store deep link verification. When fixing a deep link verification, the roadblock was the .well-known/assetlinks.json. The in-app AI suggested contacting support, which I did, and it came back with this: see below. There are workarounds; it would help many builders to have this integrated already. Thanks for reaching out. I completely understand what you're trying to accomplish — the .well-known/assetlinks.json path is required for Android App Links (Digital Asset Links) verification with Google Play. Unfortunately, I'm not able to configure custom URL rewrites or routing rules on your behalf — this isn't something support agents can do directly on the platform side. That said, here's a workaround that should achieve the same result without needing a URL rewrite: The approach: Instead of a rewrite, you can make your assetlinks backend function responds directly to the correct path by serving the JSON content in a way Google Play can verify. However, since Base44 functions are served under /functions/ , the path won't match .well-known/assetlinks.json directly. The most reliable workaround is to host the assetlinks.json file externally and point to it. Here are your options: Host on GitHub Pages or similar — Upload your assetlinks.json to a static host and serve it at the exact .well-known/assetlinks.json path, then use a redirect from your Base44 app if possible. Try asking the AI chat with a more specific prompt — Sometimes framing the request differently helps: Create a backend function that serves the assetlinks.json content needed for Google Play Store deep link verification. The function should return the correct JSON with Content-Type: application/json headers. Then in Google Play Console, you can sometimes specify a custom assetlinks URL path. Use a Cloudflare Worker or similar proxy — If your domain DNS goes through Cloudflare, you can add a Worker or Page Rule that intercepts /.well-known/assetlinks.json and proxies it to your Base44 function. I'd also suggest submitting this as a feature request on the Base44 Feedback board — custom path routing / URL rewrites for well-known paths is a legitimate need for app store integrations and would benefit many builders.

Zana Grant 1 day ago

💡

Feature Request

I have my entire schema (180 tables) saved as individual SQL files and building an ADMIN CRUD in Base44. The “workaround” to re-save them all as .txt is silly. This is a simple feature request. Enable .sql as an upload file type. Should be super simple!

Geoff Hoffman 1 day ago

💡

Feature Request

You should be able to have multiple conversations with your AI agent so that you can request several tasks at once. Additionally, you should have the option to start a new chat and delete the old one, but this should affect the agent's memory or knowledge.

Shlome 1 day ago

💡

Feature Request

so i have been using credits on repairs and now i just lost over a 100 due to the no rollover policy this is frustration due to i was at the max amount and ran out then adjusted and now i was charged for a new month and lost the ones that i did have and feel like they should be able to stay with you it is forcing me to pay in steps use run out and upgrade and i feel that is not the way it should be if you pay for something you should not loose especially that you don’t have a bigger plan not that i want to pay it but as you get involved in a project and run out you cant save up credits for a big project in the future

spacecoastwatersweep@yahoo.com 1 day ago

💡

Feature Request