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

Version 2.4: The Biggest Update to Free App Maker Yet

When we launched Free App Maker, the core promise was simple: paste your URL, click build, get a signed APK in about 60 seconds. Version 2.4 keeps that promise and builds around it. This release brings the My Apps dashboard for keeping track of your builds, email delivery of every finished APK, push notifications via Firebase Cloud Messaging for custom builds arranged through our team, and a one-time splash-removal unlock that also keeps your APKs available for longer. Free to start, no account. Here is everything that is new, what it actually does, and how to use it.

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 support@freeappmaker.org 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.

Why FCM? It is Google's own delivery channel for Android notifications — the same infrastructure the biggest apps on the Play Store use — and it means notifications can reach your users even when the app is closed.

The My Apps Dashboard: Complete Tour

Every app you build now shows up in My Apps — open it from the navigation on the homepage. It is deliberately lightweight: the list lives in your own browser, so there is no account to create and no password to remember. Here is what you will find inside:

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, rebuilding is free and takes about 60 seconds.

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.)

One honest note: because the list is stored in your browser rather than in an account, it will not follow you to a different device — but the download link emailed to your verified address works anywhere.

The Build Pipeline & Email Delivery

The build itself keeps its promise: paste a URL, set your app name, icon, and splash image, and get a signed APK in about 60 seconds. What v2.4 improves is everything around the build:

• Your email is verified once, with a code. Before your first build we send a one-time verification code to your address. No account and no password — the code is it.
• 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

The free builder produces a signed APK — the format you can install directly on any Android device, attach to an email, or host for download. 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 AAB is generated automatically within minutes, together with your own signing key and its password, a hosted privacy policy page, the 512×512 store icon and 1024×500 feature graphic, the store listing text, prepared answers to Google's content and Data safety forms, and a step-by-step READ-ME-FIRST guide. You then upload it yourself from your own Google 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: unlimited builds and downloads with your verified email, forever — one payment, not one payment per app
• What it costs: priced by country — ₹299 in India, R$49.90 in Brazil, and between $4.99 and $29 elsewhere; the exact price for your country is shown on the button before you pay
• 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
• Guarantee: 14-day money-back guarantee

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 (it takes about 60 seconds) and it appears 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, rebuild — it is free and takes about 60 seconds.

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. URL in, signed APK out in about 60 seconds, no account. That is the product, and it is not changing.
• 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?
No. Firebase is only involved if you want push notifications, which our team sets up with you as a custom build — contact us through the form on the homepage. A standard build from the free builder involves no Firebase at all.

Is there a Pro subscription or a monthly plan?
No. There is no subscription, no Pro tier, and no recurring charge of any kind. The builder is free to start, with no account, and there are two one-time purchases, both priced for your country and shown before checkout: the splash-removal unlock — pay once and every app you build comes out without the Free App Maker splash — and the Play Store Pack, which includes the unlock together with the AAB and the other files Google Play requires.

How long do my APK download links last?
Free builds are kept for 24 hours after the build finishes. If you have bought the splash-removal unlock, your APKs are kept for 7 days. Either way, rebuilding is free and takes about 60 seconds, so an expired link is never more than one rebuild away.

I built my app on an earlier version — do I get the improvements automatically?
Apps already installed on your users' devices keep working as they are. Every new build uses the current pipeline automatically — run a fresh build and it picks up everything on this page, no matter when you built your first app.

How do I get an AAB for Google Play?
The free builder produces a signed APK. When you need an AAB for a Play Store submission, buy the Play Store Pack for that app — from the done screen, from My Apps or from the Pack page. The AAB is generated automatically within minutes, together with your signing key, a hosted privacy policy page, the store graphics and prepared answers to Google's forms, and you upload it from your own Google Play Console.

Conclusion

Version 2.4 is Free App Maker growing into a rounder product without touching the part that matters most: the free builder stays free, no account required. My Apps keeps your builds in one place, email delivery means you never lose a link, the one-time unlock gives you clean unbranded apps with a full week of retention, the AAB comes in the Play Store Pack, and push notifications are one conversation with our team away. If you have been using the tool since the early days, rebuild and take a look around. If you are new here, start with our beginner conversion guide, and come back here once your first app is built and you are ready to take it further.