Pluna

Turn any goal into a graph you can run.

Describe what you’re trying to build. Pluna maps out what has to happen, in what order, and with which tools.

Only used to tell you when Pluna opens. Unsubscribe anytime. Privacy

An execution graph for shipping a mobile app. User interviews and core flow design lead to parallel app shell and backend build tasks, which merge into store submission.
  1. 01VALIDATE

    Interview 10 users, pick one job

    DONE
    • Calendly
    • Notion
  2. 02DESIGN

    Design the core flow and app icon

    DONE
    • Figma
  3. 03BUILD

    Make the app work offline

    IN PROGRESS
    • Expo
    • SQLite
  4. 04BUILD

    Stand up auth, storage and push

    READY
    • Supabase
    • Firebase
  5. 05SHIP

    Prep listings and submit for review

    READY
    • TestFlight
    • App Store
PROMPT
GRAPH
EXECUTE

The goal

Write it how you say it.Pluna handles the rest.

Your prompt

Build an offline-first mobile app for field technicians, launch on iOS in six weeks, under $200/month in infrastructure.

What Pluna picked up

  • CONSTRAINToffline-firstLocal storage and a sync layer become part of the build, not an add-on
  • USERfield techniciansNarrows the scope to one audience, so every feature is judged against it
  • PLATFORMiOSEvery release has to clear App Store review first
  • DEADLINEsix weeksThe date holds, so scope is what gives
  • BUDGET$200/monthRules out anything you would have to host and run yourself

The work

A task tells you what. Pluna tells you how.

Each step comes with where to start, which tools to use, and what done looks like.

A to-do list gives you this

Make the app work offline

Pluna gives you this

03 · BUILD

Make the app work offline

IN PROGRESS

TOOLS
  • Expo
  • SQLite
REQUIREMENTSWorking sign-in, and an agreed list of what data syncs
OUTCOMEThe app runs fully offline and syncs pending changes when the connection returns

How to approach it

  1. 01

    Lay out the routes and screens

    The shell comes first, so the data layer plugs into a structure that already works.

  2. 02

    Define the local schema and its migrations

    These tables are what the interface reads from, so they have to match what syncs back.

  3. 03

    Read every screen from the local database

    Screens render from what is already on the device, so nothing waits on the network.

  4. 04

    Write locally first, then queue the change for sync

    A connection lost mid-edit leaves the app consistent and the change still pending.

  5. 05

    Replay the queue in order when the connection returns

    Edits applied out of sequence are the usual cause of records ending up wrong.

The change

Your constraints change. Your plan can change with them.

Infrastructure budget

Managed auth, storage and builds. Enough to ship without running servers.

  1. 01 · VALIDATE

    Interview 10 users

    CalendlyNotion

  2. 02 · DESIGN

    Design the core flow

    Figma

  3. 03 · BUILD

    Build app shell and sync

    ExpoSQLite

  4. 04 · BUILD

    Auth, storage and push

    Supabase ProFirebase

  5. 05 · SHIP

    Prep store listings

    EAS BuildTestFlight

Be first in when Pluna opens.

Only used to tell you when Pluna opens. Unsubscribe anytime. Privacy