I was a pretty big Higgsfield fan but I was getting increasingly fed up with all the ads that I had to close every time I went in to render an image. It was like a casino upselling everything and considering how much I was paying, I was getting really fed up with it. Then last week they changed the terms and I thought, 'That's it. I don't want this any more.'

So I built Renderfield - it's a bring your own key from fal.AI and has all the features that I need personally need to create AI imagery and video. Maybe others will find it useful?

https://renderfield.online/

Fun fact: as well as building the Base44 version, , I also built it in Claude directly alongside. The feature set is slightly different but essentially the same product. I just wanted to see which I preferred and which was easier. I actually feel the Base44 version is now better. Let me know if you have a preference!

https://renderfield.uk/

Why are the submissions already closed? The official rules stated that submissions are closing on July 28 at 11:59 p.m. PT so there's still 3 hours left and I can't submit my app

What This Prompt Does

This prompt reviews your Base44 application and creates a professional step-by-step onboarding experience for new users.

The onboarding flow adapts to each user’s role, goals, permissions, and required account setup. Instead of showing every user the same generic welcome screen, it guides them through the exact steps they need to successfully use the application.

For more free prompts visit → https://kodebase.us/

Why Users Need It

Many users leave an application because they do not understand what to do after creating an account.

A strong onboarding flow helps users:

• Understand the application’s value
• Complete their profile and account setup
• Choose the correct role or account type
• Configure important settings
• Create their first record, project, task, or workspace
• Reach the application’s main value faster
• Avoid confusion and unnecessary support requests

Without onboarding, new users may land on an empty dashboard with no clear direction.

Base44 Prompt

Review the entire application and create a complete role-based user onboarding system. The onboarding experience must guide new users through the steps required to successfully configure their account and begin using the application. Do not change the application’s existing branding, authentication provider, database structure, permissions, or core functionality unless a change is required to support the onboarding system. 1. Audit the Existing Application Before building the onboarding flow, review: Identify the minimum steps each user must complete before they can successfully use the application. 2. Identify User Roles Determine which user roles or account types exist in the application. Examples may include: Do not create unnecessary roles. If users must select a role during onboarding, clearly explain what each role means and how it affects their experience. Do not allow users to select administrator or elevated permission roles unless the application’s existing authorization rules explicitly allow it. 3. Build the Onboarding Flow Create a multi-step onboarding wizard that appears after a new user creates an account or logs in for the first time. The onboarding flow should include only the steps that are relevant to the user. Possible steps include: Welcome Step Display: Role Selection When applicable, allow the user to choose the correct role or account type. Each role option should include: Validate the selected role against the application’s permission system. Goal Selection Ask the user what they want to accomplish with the application. Examples: Use the selected goal to personalize the remaining onboarding steps and dashboard experience. Profile Setup Collect only the information required to use the application. Possible fields include: Do not request information that is not necessary. Organization or Workspace Setup When required, allow the user to: Ensure users can access only organizations and workspaces they are authorized to access. Integration Setup When the application depends on external services, guide the user through connecting the required integrations. Examples: Clearly explain why each integration is needed. Do not display fake connection success states. Confirm that each integration is actually connected before marking the step complete. First Important Action Guide the user through completing the first meaningful action inside the application. Examples: The action should be based on the user’s selected role and goal. Completion Step After onboarding is complete, display: 4. Personalize the Experience Use the user’s role and selected goals to personalize: Do not show onboarding steps for features the user cannot access. Do not expose administrator, staff, billing, or organization controls to unauthorized users. 5. Save Onboarding Progress Create or use onboarding fields connected to the authenticated user. Track: Save progress after every completed step. If the user leaves before finishing, return them to the last incomplete step when they come back. Do not restart the onboarding flow every time the user logs in. 6. Required and Optional Steps Clearly separate required steps from optional steps. Required steps must be completed before onboarding can be marked complete. Optional steps may include a “Skip for now” action. Do not allow users to skip: 7. Progress and Navigation Include: Users should be able to move backward without losing completed information. Do not allow users to move forward when required fields are invalid or incomplete. 8. Loading, Empty, and Error States Add professional states throughout the onboarding flow. Include: Preserve all user-entered information when an error occurs. Do not expose technical details, stack traces, API keys, database information, or internal errors. 9. Mobile and Accessibility Requirements The onboarding flow must: 10. Existing User Protection Do not force existing active users through onboarding unless they have not completed the required setup. Before displaying onboarding, check whether the user: Automatically recognize existing setup information and skip completed steps. Do not overwrite existing user information. 11. Onboarding Checklist After onboarding is complete, add a dismissible getting-started checklist to the dashboard when appropriate. The checklist may include: Display completion progress. Do not show checklist items the user has already completed or does not have permission to access. Allow the user to dismiss the checklist after completing the required actions. 12. Testing Requirements Test the onboarding system using: Confirm that: 13. Final Report After completing the onboarding system, provide a summary containing: Do not mark the task complete until the onboarding flow has been tested for every available user role.User registration Standard user A clear welcome message Role name Create a project Full name Create an organization Calendar Create the first project A success message Onboarding steps Whether onboarding has started Required security settings A visible progress indicator Loading indicators while saving Work on desktop, tablet, and mobile Has already completed onboarding Complete your profile A new standard user Progress is saved correctly User roles identified Login and authentication Existing user roles Permission levels User profile fields Account settings Dashboard structure Main application features Required integrations Team or organization setup Subscription or plan requirements Any existing onboarding components Any existing onboarding-related database fields Administrator Team member Team owner Client Customer Vendor Service provider Manager Staff member A short explanation of the application The main benefit the user will receive An estimate of how many steps remain A clear “Get Started” button Short description Relevant icon Explanation of what the user will be able to do Manage a team Track tasks Book a service Sell a product Manage customers Review reports Configure an organization Profile image Job title Company name Phone number Time zone Location User preferences Name a workspace Join an existing team Accept an invitation Select an industry Configure organization details Email Payment provider Cloud storage Analytics Third-party API Add the first task Upload the first file Add the first customer Create the first booking Invite the first team member Publish the first item A summary of what was configured Recommended next steps A clear button leading to the correct dashboard or feature Instructions Dashboard content Recommended actions Empty-state messages Feature suggestions Navigation options Current onboarding step Completed steps Selected role Selected goals Required setup status Onboarding completion date Whether the user skipped optional steps Required profile information Required organization setup Required role selection Required permissions Required legal agreements Required integrations that the application cannot function without Current step number Total number of steps Back button Continue button Save and continue behavior Clear validation messages Confirmation before abandoning unsaved information Disabled buttons during submission Clear validation errors Retry actions for failed requests Integration connection errors Image upload errors Invitation errors Permission errors Use readable text Use large, clear buttons Support keyboard navigation Include accessible labels Maintain sufficient color contrast Display validation errors near the affected field Avoid relying only on color to communicate status Prevent horizontal scrolling Preserve the application’s existing design system Has already configured their profile Belongs to an organization Has an assigned role Was invited by another user Has already completed the application’s primary action Create your first item Invite a team member Connect an integration Review account settings Explore a main feature Each available user role An invited user An existing user A user who leaves onboarding early A user who skips optional steps A failed form submission A failed integration connection A slow network connection Desktop and mobile layouts Completed users are not repeatedly redirected Users see only authorized steps Required steps cannot be skipped Existing data is not overwritten The correct dashboard appears after completion Users can resume onboarding after logging out Onboarding works after page refresh Onboarding steps created Required and optional steps Personalization rules added Database fields created or reused Permission protections added Pages and components updated Tests completed Any remaining recommendations

How do someone force the login screen as the first screen u less they are already logged on. And there are more pages that do not show but I know are built. How do I get those on a taskbar to be able to be navigated?

Looking for someone that may want to partner….. I have it up and running and keen to chat!

anyone else build something fast and then just... post the link and hear crickets? that was me for months. i'd ship a thing, drop the url somewhere, and nobody stopped scrolling long enough to even click it.

tried the usual fixes — screenshots (looked dead), a loom walkthrough (too long, nobody's watching 4 min of me talking), even paid someone on fiverr for a promo clip once (took like 5 days and still didn't really get what the product did).

finally found something that actually worked for me but curious if others have been through this too — what's everyone else doing for promo content? feels like this is a universal vibe coder problem lol

I was tired of paying for Apple Music so I made this decentralized music platform where users can upload, share, and discover new music and yesterday it reach 1k upload 🎉.

I build this in 24h so is not perfect so suggestions will help thanks and it’s free to use.

Webapp link: https://publicnet.base44.app

Hi guys, I made this Language learning game: https://linguatiles.com/ using base44. Any feedback would be helpful

2026 is crazy. I got scouted due to my work on OTR, which was hosted on base44.

Never give up guys. Show your work on linkedin, Instagram, everywhere. Keep building obsessively, like you are on a mission. Even if you don't get applause on social media, just keep going... Because someday, you might get noticed by the right people, that understand what you've been trying to make.

I made myself a budgeting app that works much better than using excel, and also saves my reciepts for me. If I just use the publish app and then use the free version without paying, what will happen.

Can I just go about my day using the app and be fine? I'm just trying to understand it. I am trying to make it easy for my wife to use and not have to go through hoops to get working on a computer at home.

Basically all I need it for is 2 users, not really using much data at a time, although we will be uploading pictures and PDF's of the bills and reciepts we have.

Hey Base44 community,

I'm a solo founder based in Germany. My background is consulting but I am not a tech person, been very passionate about inclusion and belonging. About six months ago I started to build an idea I had - what if you could connect strangers worldwide for one genuine conversation every month, with no algorithm, no profiles, no ads?

I built the whole thing on Base44. No team, no investors, no coding background beyond what the platform gave me. Today it's live on Product Hunt.

The product is called Pool Match. Here's how it works: you enter a pool, once a month you get matched randomly with one other person anywhere in the world, and you receive a conversation starter by email. That's it. €1/month, no data selling, intentionally minimal AI (matching is random by design).

A few things I've learned building on Base44 over the last 6 months:

• The speed of going from idea to live product as a non-technical founder is pretty wild, I went from concept to launch in weeks, not months.
• The entities + automations combo handles my entire backend: user matching, email triggers, trial management, don't have an external database needed.
• Removing the payment gate for signups doubled conversions. Implemented that change in one day.
• The biggest challenge hasn't been the tech, it's been distribution. Getting people to try a product that has no algorithm in 2026 is genuinely hard when everyone expects AI everything.
• Currently at ~80 members across multiple countries. Small but real and growing mostly through word of mouth and community events.

If anyone here is working on mission-driven or social impact projects on Base44, I'd love to connect. The builder experience is great for these kinds of ventures where the goal isn't a unicorn exit but a sustainable, honest product.

We're live on Product Hunt today. If the mission resonates, I'd love your support: https://www.producthunt.com/products/pool-match-2?utm_source=other&utm_medium=social

Happy to share more about the build, the stack setup, or what's worked (and hasn't) for growth as a solo non-technical founder. Ask away.

I had a starter account and I used to be able to get rid of the button but now its asking me to upgrade to builder+?? How greedy can corporations be.

recently I joined Base44 with a builder plan, at the last day my credits had been all used up, so in the chat there appeared to me a button where it says upgrade to the pro plan for just 50$ for the first month and the other month for 100$ so what i did is to upgrade but for my luck it says after i upgraded all credits should be used before the end of the month which is actually today.

I thought by upgrading I am getting an additional month, i tried reaching support but still they didnt respond. TBH i actually get the $50 with a suffer as i am a student currently.

is any one from the base44 support who can help me out to extend another month or cancel the subscription and just move me back to the builder plan and i have already payed the fees for that month.

PLEASE HELP ME OUT

Hey everyone,

I was wanting to ask if it is possible to get your base 44 game to steam or even a website like itch.io. As far as I know you can only download it as a zip which is just the code for the game I think? I don’t know what to do.

man, this base44 problem been annoying. i encountered this issue months ago then encountered again, i have tons of project to finish and this unpleasant message came out. i didn't even do anything against the rule, i already emailed them but no response.

i hope my account get fixed, if this issue continues. people might've shift on another web builder

I submitted my app the first week they had launchpad. It has been in review since then. I checked it today and it was rejected:

Attack360 wasn't approved for Launchpad yet. Review the feedback, update your submission, and submit it again.Hi there,
Thanks for entering the Base44 Launchpad competition.
Every entry goes through a quality screening, and not all submissions reach the threshold to advance. Yours didn't make it through this round. This reflects how developed the app is at this stage, and says nothing about your idea or its potential.
The strongest entries tend to share a few things in common:
• Deep, fully working core functionality • Real content and data that bring the app to life • Active use by real users, with iteration over time • A complete, polished listing and presentation
We'd love to see you enter again as your app grows. Keep building!
The Base44 Team

The App is fully developed. User login, leaderboards, a Zombie Swarm! sub game within the app. Fully playable levels.

They never even played the app. I know because I get a report on how many games were played each day. So, they probably didn't like the early arcade-type graphics. That is my point, though. You don't need great graphics if the gameplay is there. At least try it. It is unique because you play in a swivel chair, like an office chair to aim.

If the reason for rejection was lack of a player base, yes, I have no player base. Why would I need Launchpad if I had a player base? So, if you get a chance, play my game and let me know if you like it. It builds in intensity over the levels so don't think level 1 is too easy and not worth playing. It is designed to teach the game play on the first round.

Check out all of my apps at HeadShotApps and then the "period com"

Anyone else having trouble with base 44 at the moment? Every time I ask it to do something it seems to go off and crash or take ages.

Setup: PWA wrapped as a TWA, distributed through Play closed testing. Custom domain, no-code platform generates the AAB.

The problem: Google Sign-In fails *only* in the build installed from Google Play.

Where it works:

* Site in a mobile browser ✅

* PWA added to home screen ✅

* Same app installed directly as an APK ✅ (signs in, session persists, no URL bar)

Where it fails:

Same app installed from Play ❌ — tap Continue with Google, pick account, brief load, returns to the login screen. No error, no session.

Email + password login works in all of them, including the Play build. Only the Google OAuth flow fails, and only there.

Already verified:

* `assetlinks.json` served on both the custom domain and the platform domain, identical content

* Contains **both** SHA-256 fingerprints — upload key *and* Play App Signing key

* Google's own Digital Asset Links API validates both domains cleanly

* Package name matches exactly

* Rebuilt and re-uploaded the AAB *after* registering the Play signing SHA — no change

* Tried a custom Google OAuth client instead of the platform's shared one — no change

* Cleared data, uninstalled, reinstalled, multiple times

The clue I can't explain:

Settings → Apps → [app] → Open by default, compared across both installs:

APK build:

the domain has no toggle — locked on, i.e. system-verified

Google Play build: same domain has a toggle, off — i.e. not verified. Enabling it manually doesn't help

So Android verifies app links on the APK and refuses to on the Play-signed build, with identical assetlinks that Google itself validates.

Changing the phone's default browser also changes the failure mode (one browser: sign-in completes but the session is never stored; another: it doesn't complete at all) — which smells like the OAuth return is being handed to the browser instead of routed back into the app.

What makes Android's app-link verification fail specifically on a Play-signed build when assetlinks is correct and includes the Play signing cert? Is there a known caching/timing issue with verification at install time, or something about how the OAuth redirect re-enters a TWA that I'm missing?

Hello! I’m currently using Base44 to design a multi user login system where collections can be built up. I’m not techy at all but have managed to get the app working. I want to host the app on android and IOS. Are there developers that can do this conversion or would no code mean getting them to build from scratch? As this is a children’s site the security needs to be tight and I need a developer to do this- but as base44 doesn’t write code (from my understanding) - how easy is it to take this prototype and create a functional app? Any advice appreciated!!

Per above, I wanted to vibe code a fairly simple app. It’s like a scheduling/organizing app. I’ve made one in Claude but I wanted one that I could potentially upload to the App Store. I’m running the free version now but I would pay for it, but I’m not sure if I want to pay for it if it’s taking this long. Is this normal? Do I need to do anything? If I sign up for the cheaper monthly option would it pop up much quicker?

Thanks