News

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

9 min read 2090 words By My Mind Studio
Developer coding on a laptop with multiple screens

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 an APK. Version 2.4 keeps that promise and goes far beyond it. This release introduces fully integrated push notifications via Firebase, a completely rebuilt App Dashboard for managing your builds, a significantly faster build pipeline, and an improved AAB export with R8 minification. For users who have been asking "when will you add notifications?" — your wait is over. Here is everything that is new, why it matters, and how to use it.

Push Notifications: Deep Dive

Push notifications are the feature most requested by our users since launch, and v2.4 delivers them properly — not as a workaround, but as a fully integrated, production-grade implementation using Firebase Cloud Messaging (FCM).

How to set up push notifications step by step:

  • Step 1: Create a Firebase project. Go to console.firebase.google.com and sign in with your Google account. Click "Add project", give it a name (e.g., "MyBusiness App"), and follow the setup wizard. You do not need Google Analytics enabled for notifications.
  • Step 2: Register your Android app. Inside your Firebase project, click the Android icon to add an Android app. Enter your app's package ID exactly as you used it in our builder (e.g., com.mybusiness.app). Download the google-services.json file — you will not need to upload this anywhere; our builder handles it via the credentials below.
  • Step 3: Get your Server Key. In Firebase Console, go to Project Settings > Cloud Messaging. Under "Project credentials", copy your Server Key (a long alphanumeric string beginning with "AAAA").
  • Step 4: Get your Project ID. Your Firebase project ID is shown in Project Settings under the General tab — it looks like "mybusiness-app-a1b2c".
  • Step 5: Enter credentials in our builder. In the Free App Maker configuration panel, toggle "Enable Push Notifications" to on, and paste your Server Key and Project ID into the respective fields. Build your app as normal.

What notification types are supported: Simple text notifications (title + body), notifications with a custom icon image, click-to-open-URL notifications (deep link to a specific page in your app), and silent background notifications for analytics pings.

Free vs Pro for notifications: The free tier includes push notification infrastructure in your APK build — meaning the app is capable of receiving notifications. Sending notifications requires a Pro subscription, which unlocks the in-dashboard notification sender and the broadcast API endpoint.

Pro tip: Segment your notification audiences by behaviour. Send "we miss you" notifications to users who have not opened the app in 7 days, and "exclusive offer" notifications to users who visit your checkout page. Segmented push campaigns generate 3x higher engagement than broadcast campaigns. For more on why notifications are so powerful, see our 5 reasons your website needs a mobile app article.

App Dashboard: Complete Tour

Every app you build now has a dedicated dashboard — a central hub for managing everything about your app after the initial build. Here is what you will find inside:

Build History: Every build you have ever created is logged with a timestamp, version number, configuration summary, and download links for both APK and AAB files. You can re-download any previous build at any time. This is invaluable for rolling back to a known good configuration if something changes on your website.

One-Click Rebuild: Changed your logo? Updated your website URL? The "Rebuild" button recreates your app with the same configuration but picks up any changes you make first. No need to re-enter all your settings — your previous configuration is pre-loaded and editable.

Icon and Splash Screen Update: Update your app's visual identity without rebuilding from scratch. Upload a new icon or splash screen image and click "Update Assets" to trigger a targeted rebuild that only regenerates the affected resources — saving build time.

Build History: View your previous builds and their status — all from within the dashboard.

Build Analytics: For Pro users, see aggregate data on how your builds are performing — download counts, install rates (when linked to Play Console via API), and build success/failure history.

Faster Build Pipeline: What We Optimised

The v2.4 build pipeline is measurably faster. Average build time has dropped from 75 seconds to 58 seconds — a 23% improvement — with Pro users seeing sub-30-second builds thanks to priority queue access and pre-warmed build containers.

Here is what changed technically: we introduced container pre-warming, which keeps a pool of Android build environments in a ready state rather than cold-starting a container for each build request. We also parallelised the icon generation step — previously, the 48 icon sizes required by Android were generated sequentially; now they are generated in parallel batches. Finally, we optimised the AAB assembly step to skip redundant resource compilation when assets have not changed.

For users building multiple app variants (e.g., a white-label solution for multiple clients), the cumulative time saving is significant. Building 10 apps now takes approximately the same time as building 7 apps did in v2.3.

Improved AAB Export with R8 Minification

The AAB files produced by v2.4 are 30–40% smaller than those produced by previous versions, thanks to the integration of R8 minification and resource shrinking in the build pipeline.

What is R8 minification? R8 is Android's code shrinking and obfuscation tool. It removes unused code from your app's codebase, renames classes and methods to shorter identifiers (obfuscation), and optimises bytecode. For a WebView app, the code being minified is the app shell — the native Android wrapper around your WebView component. This code is relatively compact to begin with, but R8 still achieves meaningful size reductions.

Resource shrinking is the other half of the equation: unused image assets, string resources, and layout files that are referenced in code but never actually used on any code path are removed automatically.

What this means for you: A smaller AAB means smaller APK downloads from Google Play (Google generates device-specific APKs from your AAB, and smaller source material means smaller outputs). Users on slow connections or with limited storage are more likely to complete the install. Google Play's internal ranking algorithm also gives a small boost to apps with smaller download sizes, because they correlate with lower uninstall rates.

For Play Store publishers: The combination of AAB format and R8 minification means your app's install size is now as competitive as apps built by professional development teams. See our complete Play Store publishing guide for the full submission walkthrough.

New Pro Features — Summary

  • Push notification sender: In-dashboard broadcast and segmented notification tool with scheduling
  • Priority build queue: Skip the free tier queue — builds complete in under 30 seconds
  • AAB export: Required for Google Play Store new app submissions
  • Build history and one-click rebuild: Full version management for your apps
  • Unlimited app builds: Free tier is limited to 3 builds per month; Pro is unlimited
  • Icon and splash screen updates: Change visual assets without full rebuild
  • Analytics dashboard: Build performance and (for Play Console-linked apps) install analytics
  • Priority support: Email support with a guaranteed 24-hour response time

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 v2.4 features, rebuild your app. Log in to your dashboard, find your app, and click "Rebuild". Your settings are pre-loaded. Add your Firebase credentials if you want push notifications, then build.
  • 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.
  • Old download links still work. Your previous APK download links remain active in your build history for 90 days after your last build.

Bug Fixes in v2.4

  • Fixed: Splash screen not disappearing on slow connections. On devices with very slow internet, the splash screen would sometimes remain visible even after the WebView had begun loading. This was caused by a race condition in the page-load detection logic. Resolved with a fallback timeout mechanism.
  • Fixed: App crashing on Android 7 (Nougat) devices. A dependency update in v2.3 introduced an incompatibility with Android API level 24. Affected approximately 3% of our user base. Resolved by pinning the affected library to a backward-compatible version.
  • Fixed: Icon blurriness on high-density screens. Apps built with icons supplied at exactly 512x512 pixels were displaying slightly blurry icons on xxxhdpi screens (4x density). The icon generation pipeline now applies supersampling for density targets above xxhdpi.
  • Fixed: External links opening inside the app instead of the browser. Links with target="_blank" and certain redirect patterns were incorrectly being intercepted by the WebView navigation handler and opening inside the app instead of the system browser. URL classification logic has been improved to correctly identify and route external links.

Product Roadmap: What Is Coming Next

Here is what the team is working on, with expected timelines:

  • iOS IPA export (Q3 2026) — Build an iOS app from the same configuration as your Android app. This has been the single most requested feature since launch. It is in active development and on track for a Q3 2026 beta.
  • QR code generator (Q2 2026) — Automatically generate a branded QR code linking to your APK download or Play Store listing, ready to embed on your website or print on materials.
  • In-app update prompts (Q3 2026) — When you publish a new version of your app, users on old versions will see a prompt to update. Currently, Play Store handles this automatically, but direct APK users have no update mechanism. This feature closes that gap.
  • White-label builder (Q4 2026) — Agencies and resellers will be able to offer app building under their own brand, with custom domains, logos, and client management tools.
  • In-app purchase support (2027) — Integration with Google Play's billing API to allow your app to sell digital products and subscriptions directly.
Beta access: Want early access to iOS export or white-label features? Contact our team — active users are the first to be invited into beta programmes for new features.

Frequently Asked Questions

Do I need a Firebase account to use v2.4?
No. Firebase is only required if you want to enable push notifications. If you do not need notifications, you can build your app exactly as before with no Firebase account needed.

Will my push notifications keep working if I cancel my Pro subscription?
If you downgrade from Pro to Free, the push notification sending dashboard becomes unavailable. However, apps already installed on user devices remain capable of receiving notifications sent directly via the Firebase API. You lose the convenience of the in-dashboard sender, not the underlying functionality.

What does R8 minification do to my website content?
Nothing. R8 only affects the native Android app shell code — the Java and Kotlin code that wraps your WebView component. Your website's HTML, CSS, and JavaScript are loaded at runtime from your server and are completely unaffected.

I built my app on v2.2 — do I get the faster builds automatically?
The faster build pipeline applies to all new builds regardless of when your account was created. Simply rebuild your app from your dashboard and you will get the v2.4 pipeline speed.

When will iOS support be available?
iOS IPA export is our top development priority and is targeted for Q3 2026 beta. Pro users will receive early access invitations by email. The challenge with iOS is Apple's strict code-signing requirements — unlike Android, you cannot freely distribute iOS apps as files, so the iOS export will produce a signed IPA configured for TestFlight distribution or App Store submission.

Conclusion

Version 2.4 is not an incremental update — it is Free App Maker becoming a complete platform. Push notifications bring your app to life as a communication channel. The App Dashboard makes managing your apps professional and effortless. The faster build pipeline respects your time. And the improved AAB export makes your Play Store submissions smaller and more competitive. If you have been using our tool since the early days, now is the time to rebuild and unlock everything that is new. 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.

Turn your website into an Android app — free

Paste your URL, get a signed APK in about 60 seconds. No signup, no card, no catch.

Build My App — Free →