Quick Start Checklist

Step 1: Prepare Your Base44 App

Before connecting to BuildNatively, make sure your app is ready.

• Your Base44 app is published with a secure HTTPS URL (required by iOS/Android).

• Your app uses one primary domain for all internal pages.

• Each key page (login, signup, profile, checkout, dashboard) has its own unique URL.

• Avoid popups/modals for critical actions (login, payments). Use full pages where possible.

• Test your app on a real phone browser:

  • Check that text, buttons, and forms look good on small screens.

  • Fix anything that looks cut off, too wide, or hard to tap.

• If you use Social Login (Google, Apple, Facebook), note that you’ll need to enable Universal Links in BuildNatively.

• Make a list of external links (Stripe, YouTube, Calendly, external docs). These will be configured as external later.

---

✅ Step 2: Set Up Your Mobile App in BuildNatively

• Log in to your BuildNatively dashboard.

• Click Create New App.

• Enter your app’s name.

• Paste your Base44 HTTPS URL.

• Save the app.

Now your Base44 app is linked to BuildNatively!

---

✅ Step 3: Customize Your App

• App Icon: Upload a 1024×1024 PNG (no transparent background).

• Splash Screen: Upload a 2048×2048 PNG (shown while the app loads).

• Error Screen: Upload another 2048×2048 PNG (shown if network fails).

• Navigation: Choose between Bottom Bar, Top Bar, or no navigation bar. Add tab links if using a bottom bar.

• Colors & Style: Adjust background, accent colors, and overall appearance.

• Permissions: If your app uses location, camera, microphone, etc., write clear permission descriptions (example: “We use your camera to let you upload a profile picture”).

---

✅ Step 4: Configure Links

• Add your Base44 domain as Internal so it stays inside the app.

• Add all third-party sites (Stripe, Calendly, YouTube, external help docs) as External so they open in the user’s phone browser.

• This prevents users from getting “stuck” when leaving your Base44 site.

---

✅ Step 5: Enable Native Features (Optional, But Powerful)

• Push Notifications: Set up OneSignal or Firebase. Use deep links to send users to exact screens when they tap a notification.

• Deep Links (Universal Links): Required for Social Login (Google, Apple, Facebook) and helpful for opening specific screens from links.

• In-App Purchases: Use if selling digital content/subscriptions (via RevenueCat).

• Other Features: Enable extras like geolocation, camera, QR scanner, contacts, haptics, or analytics depending on your needs.

---

✅ Step 6: Test Your App

• Download the BuildNatively Preview App on your phone.

• Log in and preview your Base44 app.

• Check layout, navigation, and page flow.

• Remember: some features (push notifications, Social Auth, deep links, in-app purchases) will only work after a full build.

---

✅ Step 7: Build & Publish

• In your BuildNatively dashboard, create your iOS and Android builds.

• For iOS:

  • Connect your Apple Developer account.

  • Test in TestFlight.

  • Submit to the App Store.

• For Android:

  • Connect your Google Play Developer account.

  • Upload the APK/AAB to Google Play Console.

  • Publish to the Play Store.

---

✅ Step 8: After Publishing

• Update your Base44 app anytime — changes appear instantly in your mobile app (no rebuild needed).

• If you change native features (push notifications, payments, deep links, navigation), rebuild in BuildNatively.

• Use push notifications and deep links to keep users engaged.

• Track usage with analytics if enabled.

---

Pro Tips for Success

• Keep your app lightweight — optimize images and videos in Base44 for faster load times.

• Use mobile-first design in Base44 to make sure everything looks good on phones.

• Always mark checkout/payment links as external to avoid errors.

• Write clear permission descriptions to prevent App Store rejections.

• Plan to test login, payments, and notifications on real devices before submitting