Free App Maker v2.4: Push Notifications, App Dashboard & More

Version 2.4: The Biggest Update to Free App Maker Yet

Version 2.4 introduced My Apps, email delivery and longer APK file retention for paid builds. This changelog explains those features and how to use them with the current builder.

Push Notifications: Available on Request

Push notifications have been among the most requested capabilities since launch, and v2.4 is when they arrived — with one honest caveat: push is not a self-serve toggle in the builder. It is delivered through Firebase Cloud Messaging (FCM) as part of a custom build that our team prepares with you.

How it works:

• A standard build involves no Firebase at all. If you do not need notifications, nothing changes — paste your URL and build exactly as before.
• When you want push, tell us. Reach out through the contact form on the homepage or email hello@mymindstudio.ai and describe your app and what you want to send.
• We configure FCM into your build. Our team handles the Firebase Cloud Messaging integration and walks through the setup with you, so your Android app can receive notifications like any native app.

Firebase Cloud Messaging supports notification delivery when the app is in the background. Users may need to grant Android notification permission. Sending credentials belong in a trusted server environment, as described in Firebase’s authorization guidance.

The My Apps Dashboard: Complete Tour

Open My Apps from the homepage. Verify the email address you used for your build to recover the history linked to that address, including on another device. No password is needed.

Your builds, in one place: Each app you have built is listed with its name, its icon, and the website it wraps — newest first — so you can tell your builds apart at a glance.

Re-download: A Download button next to each app fetches the APK again for as long as we keep the file — 24 hours for free builds, 7 days once you have bought the splash-removal unlock. If a link has expired, start a fresh build using the saved settings when available.

The unlock, right where you need it: If you decide to remove the "Made with Free App Maker" splash, you can buy the one-time unlock straight from My Apps — no need to start a new build first. After paying, a one-click rebuild produces the clean APK from the settings you already entered.

A direct line to the team: Need push notifications or custom features? The contact button inside My Apps goes straight to us. (The AAB is not a request — it comes in the Play Store Pack, bought from My Apps.)

Check that you are using the same email address when switching devices. An expired APK still needs a fresh build even if its entry remains in your history.

The Build Pipeline & Email Delivery

Paste a URL, add the app details and verify your email to build. Here is how you receive and recover the result:

• Verify by email. We send a one-time code when verification is needed. You can use the same address to recover your build history.
• The download link is emailed to you. When your build finishes, we email the link to your verified address — so you do not have to sit watching the tab, and you cannot lose the link by closing it.
• Resend, safely. From the finished-build screen you can send the link again. For security it can only go to the email address you verified.
• Links now survive our own deploys. Finished APKs are archived, so an emailed link keeps working for its full promised window even when we ship a new version of the build server (details in the bug fixes below).

AAB Export: Included in the Play Store Pack

A signed APK is an installable file for compatible Android devices. Building is free, with a one-time payment to unlock APK downloads. Google Play, however, requires the AAB (Android App Bundle) format for new app submissions: it is a publishing format that lets Google generate smaller, device-specific APKs for each install.

How to get an AAB: when you are ready to submit to the Play Store, buy the Play Store Pack for that app — from the done screen, from My Apps or from the Pack page. The pack includes the AAB and supporting files for that app, including key material and listing and policy drafts. Keep the key material private. Verify the drafts for your specific app before you upload from your own Play Console.

The One-Time Unlock — Summary

There is no subscription and no "Pro" tier. There are two one-time purchases — this unlock, and the Play Store Pack, which includes the unlock along with the AAB and the other files Google Play requires. The unlock:

• What it does: removes the small "Made with Free App Maker" splash that free builds show, from this app and every app you build after it
• What it covers: the APK download unlock is linked to your verified email. The Play Store Pack is purchased separately for each eligible app
• What it costs: your local one-time price is shown before checkout
• Longer retention: your APKs are kept for 7 days instead of 24 hours
• One-click clean rebuild: straight after paying, one click rebuilds the app you just configured without the splash — no re-entering settings
• Refunds: check the refund policy for eligibility and support

Migration Guide for Existing Users

If you built an app using a previous version of Free App Maker, here is what you need to know about upgrading:

• Your existing APKs still work. Apps already installed on users' devices will continue to function normally. The v2.4 changes only affect new builds.
• To get the newest pipeline, rebuild. Every new build uses the current pipeline automatically — run a fresh build and check it in My Apps alongside your earlier ones.
• Package ID must stay the same for updates. If you are updating an app already on Google Play, make absolutely sure your package ID is identical to the one in your Play Console listing. A different package ID creates a new app, not an update.
• Download links have a defined lifetime. Free build links last 24 hours; unlock holders' links last 7 days. After that, start a fresh build.

Bug Fixes in v2.4

• Fixed: emailed download links dying early. Deploying a new version of our build server used to wipe finished APKs, which could kill an emailed download link long before its promised lifetime. Finished builds are now archived so every link lasts its full window.
• Fixed: paying customers' APKs being cleaned up early. Storage cleanup could remove an unlock holder's APK before the 7-day promise was up. Paid builds are now protected from storage-cap cleanup for the full period.
• Fixed: duplicate rows in My Apps. Returning from checkout could add a second entry for the app you had just built. One build now shows as exactly one row.
• Fixed: the unlock dialog not appearing from My Apps. Downloading a splash-gated build from the dashboard could fail silently instead of offering the unlock. The dialog now opens reliably wherever the download starts.

Product Roadmap: What Is Coming Next

We deliberately do not publish feature dates we are not certain we can hit — a changelog should be a record, not a wish list. What we can tell you about where the product is going:

• The free core stays free. Build from your URL after verifying your email. The APK download uses a one-time unlock.
• New capability ships as a product or as custom work. AAB export is included in the Play Store Pack today; FCM push notifications are set up with our team on request, and fully custom apps are built the same way. If demand keeps growing, the most-requested of these graduate into the builder itself.
• Free tools keep growing. The WebView Compatibility Checker, Package Name Generator, Privacy Policy Generator, and App Icon Generator are all live — free, no account.
• Your requests steer the roadmap. The quickest way to influence what we build next is to tell us what you need through the contact form.

Frequently Asked Questions

Do I need a Firebase account to use v2.4?
The standard builder does not require you to set up Firebase. If you need push notifications, ask about a custom build.

Is there a Pro subscription or a monthly plan?
There is no monthly plan for the APK unlock. Building is free after email verification. Pay once to unlock APK downloads for that verified email. Buy the Play Store Pack separately for each eligible app that needs publishing files.

How long do my APK download links last?
APK file retention is 24 hours for free builds and seven days for unlocked builds. If the file has expired, start a fresh build from the saved details when available.

I built my app on an earlier version — do I get the improvements automatically?
The installed version does not update just because you rebuild. To update an existing app, keep the same application ID, increase its version code and follow the signing requirements for your distribution route.

How do I get an AAB for Google Play?
Buy the Play Store Pack for the eligible app that needs an AAB. Check the supporting files and submit from your own Play Console.

Conclusion

If you built an app earlier, open My Apps and verify the original email address. Rebuild if the APK link has expired. If you are starting fresh, follow the Android conversion walkthrough to test your site before paying to download.