NAAPY STUDIO · FOR REACT NATIVE DEVELOPERS

Stop scope creep. Start building.

Send your client the screens and the plan. They ask for changes or approve, on their phone. Every request is logged, and version 1 is locked before you build.

For React Native / Expo freelancers building paid client apps.

A TICKET APP · AN EXAMPLE CLIENT BRIEF

THE BRIEF

“A ticket app for the shows in our city: show what’s on, let people pick their seats and pay, and send them the ticket.”
Naapy drafts the plan. You correct it.

THE PLAN

In this buildWhat’s on and show pages, Pick seats, Pay and get the ticket

Not in this buildSeason stats, Gift cards, Waitlists

Approved by Henrietta, round 2 · Version 1 locked

THE SCREENS

THE REALITY OF CLIENT WORK

It’s never “just an app.”

Your client sees a few screens. You see everything that comes with them.

“Can you build a simple ordering app?”
  • Login
  • Orders
  • Payments
  • Changes
  • Release

And when they change their mind, nobody can show what they agreed to.

BEFORE YOU WRITE CODE

Get it signed off. Then build.

Invite your client by email. They open the screens and the plan on their phone, point at the exact screen or feature they want changed, and approve when it is right.

INVITE · AN EXAMPLE

SHARE · INVITE BY EMAIL

henrietta@example.com

Can reviewCan edit

Invite

Invitation sent to henrietta@example.com.

Your client signs in free. No app to install, none of your credits.

YOUR PROOF

Every request, on the record.

You and your client see the same log: every round, every request, every approval, with the date. When a new request arrives after approval, it goes on the next-version list, not into this build. That is where your next quote starts.

If the screens or the plan change after an approval, the approval shows as out of date. Nobody can approve one version and be held to another.

ACTIVITY · AN EXAMPLE

  • Round 1 sent
  • Screen: Pick your seatsCan we show the price on each seat?
  • Plan: Feature 4Add a waitlist for sold-out shows.
  • Round 2 sent
  • Approved by Henrietta, round 2
  • Version 1 locked
  • Next versionGift cards for Christmas?

HOW IT WORKS

One brief. A whole head start.

Make the plan clear, get your client’s sign-off on the screens, and build the app with its backend.

  1. 01

    Plan it

    Decide what belongs in the first build.

    The plan you approve
  2. 02

    See it

    Answer a few questions, then click through your screens.

    The screens you review
  3. 03

    Get sign-off

    Your client asks for changes or approves.

    TICKET APP · ROUND 2

    01Approved by Henrietta
    02Version 1 locked
    new requests wait for version 2
    The round your client approves
  4. 04

    Build & check

    Generate the app and review what worked.

    The screens you build

ONE BRIEF, START TO FINISH

See what one brief becomes.

See a brief become a plan, screens and an app with its backend.

Show page
Pick your seats
Your tickets
  • An example brief for a city’s ticket app
  • The plan is approved before any code
  • The app and its backend are checked before you open them

YOU’RE STILL THE DEVELOPER

Your code. Your call.

See what’s working, what’s unfinished, and what needs your attention. Keep the code and stay in control.

  • Preview the appOn your phone by QR, before the client sees it.
  • Inspect your codeDownload the ZIP or push it to your own GitHub.
  • Know what’s leftSee what passed its checks and what still needs work.
  • Bring in a co-developerCan edit lets them write prompts on your credits. Your code, credits and secrets stay yours.

And when it’s time to ship?

Signed release builds with EAS, a store checklist for each app, and store submission on the Pro pack. Apple and Google decide on approval.

YOUR NEXT PROJECT

Got a client brief?

Plan it, send it, get it signed off.

QUESTIONS

The details.

Does my client need to pay or install anything?

No. They make a free Naapy account with Google or an email code and review on their phone’s browser. Reviewing uses none of your credits.

What if my client asks for more after approving?

The request goes on the next-version list, in the same log. Version 1 stays locked, so you can quote the extra work.

Do I need my client’s approval to build?

No. You can build any time. The log then says “Built without approval”.

What can my client see?

With Can review: the screens, the plan and the log. Not your code, chat, credits or secrets. Can edit is for a co-developer you trust.

Who is Naapy for?

React Native / Expo freelancers who build paid apps for clients. You stay the developer: you review the plan, the screens and the code, and your client signs off on the first two.

What can I try for free?

On the Free plan, a new account gets free credits for the planning steps: drafting the plan, answering its questions and reviewing the clickable mockup. Generating the app and its backend needs a credit pack.

Can I edit and export the code?

Yes. Download your latest successful build as a ZIP, or push it to your own GitHub repository. The code is yours to change, test and ship.

What happens when Naapy gets something wrong?

It runs the checks it supports, tries to repair what fails, and checks again. Anything it could not fix is shown in the chat and in the exported README, for you to finish.

Can it publish to the App Store or Google Play?

Yes. On the Pro pack, Naapy handles App Store and Play Store submission, signed release builds and a store checklist for each app. Apple and Google decide on approval.

Which technologies does it use?

A React Native / Expo app in TypeScript, and a FastAPI backend with MongoDB. Flutter, Kotlin and Swift are not supported.