What You Get at Launch

When launching a new product in the web-to-app space, clarity is essential. Pre-launch tools often make sweeping promises about "instant AI transformation" without specifying what binary artifacts, engine capabilities, or configuration files are delivered on day one.

This guide provides a transparent, clear-eyed breakdown of what you get at launch with Craft2Native, along with explicit confirmation of what is reserved for post-launch releases.

Day-One Capabilities (Included at Launch)

On launch day, Craft2Native delivers a fully configured, store-ready Android application bundle built around your live web URL.

1. Production Binary Generation - **APK File (Android Package):** Directly installable on test devices, QA hardware, or for distribution outside the Play Store. - **AAB File (Android App Bundle):** Google's mandatory publishing format, compiled with your signing keystore and optimized for Play Store release.

2. Custom Native Branding & Shell - **App Icons & Launcher Assets:** Auto-generated adaptive icons for light, dark, and legacy Android devices. - **Native Splash Screen:** Custom branded loading screen displayed while the WebView initializes your website domain. - **Custom User Agent:** Ability to pass custom headers (e.g., `Craft2Native-Android-App`) so your web server can detect app traffic.

3. Core Engine & Connectivity - **SSL Security & HTTPS Enforcement:** Built-in SSL certificate validation to protect end-user sessions. - **Intent & Deep Link Routing:** Seamless handling of external links (social media share links, payment portals like UPI or Stripe, external authentication redirects). - **Offline Fallback Screen:** Clean, branded offline interface displayed whenever the user loses internet connectivity, replacing raw browser error screens.

4. Hardware & Push Integration - **Firebase Push Notification Support:** Configuration files (`google-services.json`) integrated for push notifications. - **Camera & Storage Permissions:** Auto-configured Android permission manifests for file uploads, photo attachments, and document scanning.

What is NOT Included at Day-One Launch

To avoid overselling a pre-launch product, here are features that will not be included on day one, but are slated for future engineering updates:

[Day-One Launch Focus]                [Future Engineering Roadmap]
- Android APK & AAB Files            - Dedicated iOS IPA Generation
- Firebase Push Notification Shell   - Built-in In-App Purchase Bridge
- Deep Links & Payment Redirection   - Dynamic Offline Page Caching Engine

To Be Confirmed at Launch: Exact version timelines for iOS packaging and native in-app billing bridges remain in active validation and will be communicated directly to early registrants prior to public release.

Honest Technical Trade-Offs & WebView Limits

A high-quality web-to-app tool must be transparent about the underlying technology stack and its boundaries:

1. Performance Bound to Web Server & Frontend Code:
2. - Because your web content renders inside a high-performance Android WebView container, your app’s initial load time and rendering speed are tied to your underlying web server response time and mobile CSS/JS optimization. A slow mobile website will remain slow inside an app shell until web performance is optimized.

1. App Store Policy Compliance (Google Play Guidelines):
2. - Google Play policy strictly rejects "bare web wrappers" that merely mirror a URL without adding mobile utility. Craft2Native addresses this by embedding native splash screens, offline retry states, custom navigation bars, FCM push notification listeners, and hardware permission manifests directly into the compiled native binary.

1. Hardware & Background Constraints:
2. - Features requiring low-level hardware access—such as background Bluetooth LE scanning, raw 60 FPS GPU 3D rendering, or persistent background service daemons—are outside the scope of web-to-app containers and require custom Kotlin/Swift engineering.

Feature Comparison Matrix

Why Honest Scope Matters

Over-promising creates friction when submitting apps to app stores. By focusing on a rock-solid Android container on day one, Craft2Native ensures your app passes Google Play Console policy reviews without rejections for broken browser wrappers or non-functional features.

If you want to understand how our scope compares to traditional custom app builds, read our guide on why turn your website into an app instead of building from scratch.

Frequently Asked Questions

What binary files do I receive when a build finishes? You receive a signed release APK (for direct testing and sideloading) and a signed AAB file (Android App Bundle) ready for direct submission to the Google Play Console.

Are iOS IPA packages included on launch day? Day-one release focuses on signed Android binaries (APK/AAB). iOS IPA packaging and Apple App Store integration are currently scheduled for a follow-up feature release.

Does launch access include push notification support? Yes. Firebase Cloud Messaging (FCM) configuration is integrated into the build pipeline so your web server can trigger push notifications directly to app users.

Register for Early Access

Craft2Native is undergoing rigorous internal build testing. By signing up now, you help shape early feature priorities and secure launch pricing.

Be first in line: Register your interest on the Craft2Native launch page to get direct updates as we approach our official release.