Vibe GuideBETA
中文EN

Understand the capabilities this project type needs and take relevant features back to the project brief.

Project typesMobile apps
MOBILE APP DEVELOPMENT

Turn a good idea into an everyday app.

An app installed on a phone. Check the value of installation, device capabilities, real-device testing and distribution prerequisites; a previous website is not required.

Check devices and distribution
Mobile apps
A daily journal
Start here →
INTERFACE EXAMPLE

Check suitability before building

01Which projects fit this form?

Frequently used phone tools needing substantial device integration or complex mobile interaction, such as field capture or offline workflows. First check whether a mobile website already suffices.

02What should be ready before you start building?

Builders with a real target phone who can start with one OS and handle packaging, permissions, distribution and update tests. A previous website is not required; a suitable local or cloud build setup is.

03Which projects should consider a different form?

Small content displays, one-off forms and occasional link-driven use where installation adds more burden than value; test a mobile website first.

04Which missing prerequisites should you resolve first?

Builders without a target device or testing route, unwilling to handle permissions/installations, or needing immediate public delivery without distribution prerequisites.

Still unsure? Try a small validation

Install a minimal version on a target phone and test the key capability, denied permissions, background/foreground transitions and relevant offline behavior. Simulator success is not device proof.

If a mobile website completes the essential task, deliver it first and revisit an app when needed.

Compare an alternative →

Apple · 测试与分发条件 ↗

This reference helps choose project form; its sections are not a second required route. Return to “Prepare the brief” on the main route to update the brief; technology selection is still “Agree on design and technology”.

Start with a small first version

01 / START
FOR EXAMPLE · AN ILLUSTRATION

A daily journal

Write about today, browse past entries, and edit the notes. Leave social features and payments for later.

Choose one platform first

Start on a real Android phone. Check requirements for the chosen distribution channel.

Three things to prepare

  • Choose Android or iPhone first
  • A real phone for testing
  • Decide whether notes stay local or sync

The route from idea to product

02 / BUILD

Finish one small step, check it through actual use, then move on. Open each step to see the expected result.

01Explain why it needs to be an app

Describe the value of installation, offline use, or phone features.

Afterwards, you should see: An informed choice between an app and a mobile website.
02Prepare a target device

Check the build requirements and target one phone platform.

Afterwards, you should see: A setup ready for real-device testing.
03Make one entry work

Create, save, and read an entry, then close and reopen the app.

Afterwards, you should see: The entry is still there.
04Handle phone-specific situations

Try going offline, declining permissions, going back, and switching apps.

Afterwards, you should see: Clear behavior when things don’t go as planned.
05Invite someone to try it

Have someone install it and complete the main task on their own.

Afterwards, you should see: A concrete list of usability issues.
06Release, then check the next update

Prepare release materials and check that an update keeps existing entries.

Afterwards, you should see: Both new installs and upgrades work.

Ask AI to check project fit

03 / PROMPT

Assess the form, without building

Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.

Plain text · Add actual material before sending to AI

After choosing: update the brief and follow the guided route →

What to check when stuck

Entries disappear after reopening

Create a test entry, close the app, and reopen. Is it still present?

  • Next check offline use and preservation after an update; record each separately.
  • Pause real-data entry and give AI the device, version, and steps to inspect storage location and write results.
Declining permission blocks the app

After declining camera or other permission, can the app return to unrelated features?

  • Allow permission and retest, checking that existing entries were not reset.
  • Ask AI for an explanation and exit path; avoid repeated prompts or demanding every permission.

Record the version, device, test data, steps, expected outcome, actual result, and failures. Keep AI execution records separate from personal trial results.

Open the hands-on acceptance and release template →

A few useful terms

04 / UNDERSTAND
Offline
What the app can still do without a connection.
Sync
Keeping information consistent across devices.
Beta
A version shared with a small group for testing.

Find the starting point

Module shortcuts

What people build · AI revenue research · 50 ideas · GitHubComplete roadmap · idea to releaseWrite down the ideaI only know I want a websitePrepare a project briefUnsure how to describe the first flowOpen an AI tool that can edit filesInstallation, sign-in, or the screen differsCreate a folder for the projectDocuments or the folder is missingOpen that folder in the AI toolAI names a different projectCreate Git history and project instructionsCommit fails or asks for identityInspect a file AI actually createdPrevious files are missingAnswer one question at a timeAI asks about unfamiliar technical termsChoose only this version’s essentialsReducing scope left only a pictureKeep the agreement in plain languageThe document is too long to reviewDescribe how people will use itAI lists features without a user flowReview a key screen before buildingThe prototype may use simulated behaviorLet AI choose from actual conditionsI do not know local versus shared storageAsk AI for the next small taskThe first task just says “build frontend”Check the runtime and start the projectInstallation or startup failsOpen the first page of the projectThe preview will not openAdjust this page onlyA visual edit changed other behaviorMake Save retain real contentCannot save, or records vanish on refreshFinish the whole flow onceThe button responds but nothing happensTry blank input and repeated clicksBlank or duplicate records appearReopen it after stoppingThe address fails the next dayCheck it against the original ideaAI says done, but I cannot use itRecord the trial feedbackThe issue happens intermittentlyPlan the fix and its passing checksAI starts fixing without a planFix according to plan and hand back for retestingThe same action still fails after a claimed fixChoose: personal use or sharingThe shared local link does not openAssess readiness for deliveryReadiness is claimed without evidencePrepare and try the deliverableInstaller or deployed application failsApprove delivery and verify the real entryIt opens locally but not for othersOptional: publish a simple page on GitHub PagesThe public URL returns 404Continue next time without starting overAI wants to start over in a new chatChoose a tool · Codex Claude Cursor Qoder TRAE Kimi pricingHomeProject typesTalking to agents · prompts and troubleshootingChoosing a stackFrontend & UI · component dictionaryGlossary · AI and development · examples and diagramsOpen the tool and verify project accessPrepare the project, version history, and AI rulesDescribe the intended interface styleHelp AI change exactly one targetBackend: storage and accessTesting: check that it worksDeployment: deliver a real entry pointMaintenance: keep the product usableWebsites & web apps · The idea, one link away.Mini programs · Build where the users already are.Mobile apps · Turn a good idea into an everyday app.Desktop apps · Make a tool for repetitive tasks.

A practical guide for beginners

This bilingual practical guide has 6 stages, 18 milestones and 31 actions. App illustrations are examples; users verify their own project results.