AI Folks
  • Courses
  • Web Of AI
  • Pricing
  • Enterprise
Log in
PreviousThe same brief in BoltNextOwn your code on GitHub

Vibe Coder · Unit 8: Build With Lovable, Bolt and Rork · Lesson 4 of 5

A mobile app in Rork

Rork builds native iPhone and Android apps from a description. Decide whether your product needs a phone app, build one screen flow, test it in the simulator, and learn what the app stores require.

Read the short notes and pictures.Do everything inside a blue frame.

Do you need an app at all?

A phone app feels like the real thing, and it is also slower to ship, harder to update and subject to store review. Decide with reasons.

Pale dots, hand-drawn. Two cards: when to build a phone app and when a web app is enough.
A phone app has to earn its place.

Build a phone app when

You need the camera, location or sensors.
You need notifications people will act on.
It must work without a connection.
People will open it several times a day.

Stay on the web when

It is used at a desk.
You want to change it every day.
You want one codebase.
Your users will not install an app for this.
Many products ship the web version first and add a phone app when users ask for it.

What Rork makes

iPhone

Native apps in Swift with SwiftUI.

Android

Native apps in Kotlin with Jetpack Compose.

Web

Web apps in Vite and React, published to a rork.app link or your own domain.

Preview

A cloud iOS simulator and Android emulator run beside the chat.

It changed, and may change again

Rork used to build apps with Expo and React Native and has moved to native Swift and Kotlin; its docs say older Expo projects still work. Bolt builds mobile apps through Expo. If you see tutorials that disagree with what is on your screen, check the date and the current docs.

Build one flow

  1. 1

    Pick the one phone job

    For an invoicing tool: photograph a receipt and attach it to an invoice.

  2. 2

    Describe that flow only

    Three screens at most.

  3. 3

    Watch it in the simulator

    Tap through it. Rotate it. Try it with long text.

  4. 4

    Add a backend if it needs one

    Rork Cloud, Supabase or Firebase. Rork Auth offers Google and Apple sign-in; Supabase Auth adds email and magic links.

  5. 5

    Sync to GitHub

    Rork has two-way sync through its GitHub App.

The app stores

Pale dots, hand-drawn. A table: iPhone goes through TestFlight then App Store review, Android needs an AAB uploaded to Google Play, web publishes to a link.
Each platform has its own path to users.

iPhone

Builds go to TestFlight for testers, then to the App Store, which reviews every app. You need an Apple developer account.

Android

You upload an app bundle (an AAB file) to Google Play, which needs a Google Play developer account.

Review takes time

Plan for days, not minutes, and for being asked to change something.

Updates

Every change goes through the same path.

Cost

Rork is credit based, and its docs say building and publishing need a paid plan. Developer accounts for the app stores are a separate cost charged by Apple and Google. Check current prices before you plan around them.

ActivityYour turnWrite it yourself first, then compare.

Decide for your product: phone app now, later or never? Give two reasons.

ActivityBuild stepA working first draft

Decide, then build one phone flow

Write your decision on a phone app, with reasons. Then, whatever you decided, build one small flow in Rork to learn the tool: up to three screens, tested in the simulator.

Done when

If your decision was "later", this small build is your starting point when the time comes.

Keep these

  • Build a phone app only when the phone adds something.
  • Rork builds native Swift and Kotlin apps, previewed in a simulator.
  • Store review takes time. Plan for it.
Previous lessonThe same brief in BoltNext lessonOwn your code on GitHub