Who's Responsible for What During Conversion

Successful software projects rely on clear expectations around roles and deliverables. When converting a website into a store-ready mobile app, confusing who handles what can lead to launch delays, store submission rejections, or missing brand assets.

This guide outlines the precise division of responsibilities between you (the website owner) and [Craft2Native](/craft2native) (the conversion platform).

Responsibility Matrix Overview

+-----------------------------------------------------------------+
|                      WEBSITE OWNER RESPONSIBILITY               |
|  - Live Responsive Website URL                                  |
|  - High-Res Branding Icons & Splash Screen Assets              |
|  - Google Play Developer Account Credentials                   |
|  - Privacy Policy & Terms Links                                 |
+-----------------------------------------------------------------+
                                |
                                v
+-----------------------------------------------------------------+
|                     CRAFT2NATIVE ENGINE AUTOMATION              |
|  - Native Android Container & WebView Runtime Generation        |
|  - Android Manifest & Security Policy Compilation               |
|  - FCM Push Token & Asset Packaging                             |
|  - Production APK & Signed AAB Binary Build                     |
+-----------------------------------------------------------------+

1. What the Website Owner Provides

As the site owner, your primary responsibility is ensuring your source web application is healthy, legally compliant, and properly branded:

A. A Live, Mobile-Responsive Website URL Your website must be publicly accessible via HTTPS (`https://yourdomain.com`). The pages should scale appropriately on mobile viewports.

B. High-Resolution Visual Brand Assets - **App Launcher Icon:** 512x512 PNG file (transparent background or solid brand color). - **Splash Screen Graphics:** High-res logo SVG or PNG to display during initial app startup. - **Brand Colors:** Primary and accent HEX color codes (`#4F46E5`) for the native status bar and loading spinners.

C. Developer Accounts & Store Listings - **Google Play Developer Account:** Google requires app owners to hold their own publisher account ($25 one-time registration fee paid directly to Google). - **Store Metadata:** App title (max 30 chars), short description, full description, privacy policy link, and contact email.

2. What Craft2Native Automates

Craft2Native handles the technical heavy lifting of compiling web configurations into native binaries:

A. Native Container Compilation - Builds the optimized Android WebView wrapper stripped of browser chrome. - Injects hardware permissions (Camera, GPS, Storage) based on your site's functional requirements. - Configures custom user-agent headers and SSL pinning security policies.

B. Asset Optimization & Manifest Injection - Automatically resizes raw logo files into all Android density buckets (`mipmap-mdpi`, `hdpi`, `xhdpi`, `xxhdpi`, `xxxhdpi`). - Compiles the `AndroidManifest.xml` file with proper intent filters for deep link capture.

C. Push Notification & Binary Signing - Packages Firebase Cloud Messaging (`google-services.json`) scripts into the app binary. - Compiles production **APK** files for internal QA testing and signed **AAB** files for Play Store submission.

Summary Responsibility Matrix

Next Steps & Early Access Workflow

By keeping deliverables clear and straightforward, you can prepare your branding assets while Craft2Native handles binary compilation.

Frequently Asked Questions

Do I need to provide my own Google Play Console account? Yes. Holding your own developer account ensures you maintain full ownership of your store listing, branding, reviews, and analytics.

Who maintains web hosting and database uptime? You remain responsible for hosting your website and backend database, while Craft2Native automates container compilation and FCM notification bridges.

Who handles Google Play Store rejection reviews if issues arise? Craft2Native generates Play Store-compliant binaries with native splash screens, offline retry states, and FCM notification shells to prevent bare-wrapper policy rejections.

Want to learn more about the technical build workflow? Read our step-by-step breakdown on how Craft2Native turns a website into an app step by step, or register your interest on our launch page.