WHOLESTACK DOCUMENTATION

This documentation is written as an operating manual for WholeStack. It explains both end-to-end workflow and control-level behavior so teams can ship apps with fewer unknowns.

The docs are organized in two layers: workflow guidance (how to go from idea to app) and UI control reference (what each control does, when it appears, and how to troubleshoot it).

• Recommended reading order for new users: Overview, Getting Started, Platform Features, Deploy, Publish App.
• For active builders: Projects and Workflows, then Troubleshooting and Failure Recovery.
• Use section anchors to deep-link exact steps inside your team documentation.

WholeStack is an app-building platform focused on speed from idea to working mobile product. You describe what you want, generate a baseline, iterate with AI and direct code edits, validate in preview, and build artifacts for release flows.

WholeStack is not a locked template builder. You keep real project files and make implementation decisions yourself while using AI and workflow tooling to reduce setup and iteration time.

What WholeStack provides today

• Prompt-based app generation.
• Project-level file editing and code iteration.
• AI conversation workflows for build/test/security flows (plan and feature gated where applicable).
• Live coding visibility while assistant responses are processing.
• Device preview workflows: Mobile Preview on Web (Agency) and Preview on your Phone.
• Project-scoped store build workflows for Android and iOS.
• Project-scoped Release & Publish workflows for Google Play and App Store Connect.
• GitHub export flows.

What is coming soon

• Expanded deploy automation beyond Expo/EAS release flows.
• Expanded automated testing and security scan workflows.

WholeStack uses credits for AI app creation and chat. The actual amount you can get done depends on which model you choose and how much follow-up iteration you do after the first app generation.

Current credit costs

• Best AI Model: 10 credits for a new app, 5 credits for each chat message.
• Basic Model: 5 credits for a new app, 1 credit for each chat message.
• Free: 20 credits per month.
• Pro: 200 credits per month.
• Agency: 800 credits per month.

Pro plan examples (200 credits)

• Two stronger app starts on Best AI Model (20 credits), 20 Best-model follow-up messages (100 credits), and 80 Basic-model cleanup/refinement messages (80 credits). Example: launch a service-booking MVP, then refine onboarding, pricing cards, and settings with a long iteration cycle.
• Five Basic-model app starts (25 credits) plus 35 Best-model messages (175 credits). Example: create several client-ready first drafts such as a fitness tracker, restaurant ordering app, booking app, marketplace app, and internal operations tool, then spend most credits polishing the strongest one.

Agency plan examples (800 credits)

• Eight Best-model app starts (80 credits), 84 Best-model follow-up messages (420 credits), and 300 Basic-model refinement messages (300 credits). Example: run multiple client prototypes in parallel while still leaving room for deeper iteration on the finalists.
• Twenty Basic-model app starts (100 credits), 60 Best-model feature/design messages (300 credits), and 400 Basic-model cleanup messages (400 credits). Example: batch-generate many lightweight app concepts, then upgrade only the most promising projects with heavier Best-model work.

Treat these as illustrative planning examples, not guarantees. A simple internal tool may need only a few follow-up prompts, while a more polished customer-facing app can consume significantly more credits during refinement.

WholeStack separates app release into two user workflows: Generate Store Build and Release & Publish. Generate Store Build creates the file you will later send to Apple or Google. Release & Publish is only for sending that file to the store after your store accounts are ready.

Quick Guide

1. 1Open Build and Publish your App inside your project.
2. 2Connect your Expo account token in Step 1.
3. 3Save the shared Expo owner in Step 2.
4. 4Complete iPhone setup if you want an iPhone build.
5. 5Complete Android setup if you want an Android build.
6. 6Use Generate Store Build to create the app file.
7. 7Only when you are ready to publish, come back and complete the store account details for Release & Publish.

Technical Guide

• Generate Store Build creates Android AAB output and iOS signed production output.
• Release & Publish submits an existing successful store build to Google Play or App Store Connect.
• Each user connects their own Expo token, and each project keeps its own Expo owner, app identifiers, signing mode, and store submission credentials.
• Google Play service account JSON and App Store Connect submission credentials are publish-only requirements, not build requirements.

Before WholeStack can create or publish a store build for you, you need to connect your Expo account. WholeStack stores your Expo access token encrypted on the server and uses it only when it runs Expo EAS build or submit for your projects.

Quick Guide

1. 1Open https://expo.dev and sign in.
2. 2Open your profile menu and go to Account settings.
3. 3Open Access Tokens and create a new token.
4. 4Copy the token.
5. 5Return to WholeStack, open Build and Publish your App, and paste the token into Step 1.
6. 6In Step 2, save the Expo owner for the project. This should be your Expo username or the Expo team name that owns the app.

Technical Guide

• Expo token = authentication. It proves which Expo account WholeStack should act as.
• Expo owner = project ownership. It tells WholeStack which Expo user or Expo team should own the app in EAS.
• Store build and publish always use the connected user token, not a shared platform Expo token.
• If your token cannot access the Expo owner saved on the project, Expo EAS build or submit will fail.

Use this guide if you want to build or publish your Android app.

Quick Guide

1. 1Choose a unique Android package name such as com.companyname.appname and save it in WholeStack.
2. 2If you only want to test the Android build, stop there and use Generate Store Build to create the AAB file.
3. 3If you want WholeStack to publish to Google Play for you, create the app in Google Play Console.
4. 4Create the Google service account JSON and paste it into WholeStack.
5. 5Complete one first manual upload in Google Play Console.
6. 6Return to WholeStack and use Release & Publish.

Technical Guide

Android build and Android publish are different. The Android store build only needs the package name and signing configuration. Google Play API credentials are only required for publish.

Create the app in Google Play Console

1. 1Open Google Play Console and sign in.
2. 2Choose Create app.
3. 3Enter the app name, default language, and whether it is an app or game.
4. 4Choose whether it is free or paid.
5. 5Finish the app creation flow and leave the app in draft if you are not ready to publish.

Create the Google service account JSON

1. 1Inside Google Play Console, open your app.
2. 2Go to Users and permissions.
3. 3Open API access.
4. 4If asked, link a Google Cloud project.
5. 5Create or select a service account in Google Cloud.
6. 6Grant that service account access to your app.
7. 7Create and download the JSON key file.
8. 8Open WholeStack, go to Build and Publish your App, Step 3 Android setup, and paste the JSON into the Google Play service account field.

Important note

Google Play requires one first manual upload before automated API submissions can work. That is why WholeStack asks you to confirm that first upload before Release & Publish.

Use this guide if you want to build or publish your iPhone app.

Quick Guide

1. 1Choose a unique iPhone bundle identifier and save it in WholeStack.
2. 2If you only want to test the iPhone build, use Generate Store Build after saving the bundle identifier and signing choice.
3. 3If you want WholeStack to publish for you, create the app record in App Store Connect.
4. 4Get the App Store Connect app ID and API key, then save them in WholeStack.
5. 5Return to Release & Publish when you are ready to send the build to Apple.

Technical Guide

iPhone build and iPhone publish are different. The store build needs the bundle identifier and signing configuration. App Store Connect app information is only required for publish.

Create the app in App Store Connect

1. 1Open App Store Connect and sign in.
2. 2Go to Apps.
3. 3Click the plus button and choose New App.
4. 4Enter the app name, primary language, bundle identifier, and SKU.
5. 5Save the app record.

Find the App Store Connect app ID

1. 1Open the app record in App Store Connect.
2. 2Look for the Apple ID or App Information area, depending on the screen Apple shows you.
3. 3Copy the app ID value and save it in WholeStack in the iPhone setup step.

Apple permissions

If your Apple account belongs to a team, make sure it has access to Certificates, Identifiers & Profiles in Apple Developer and the correct App Store Connect permissions. Without that access, store signing or submission can fail.

Release & Publish is a later step. First create a successful store build. Then add the store account details WholeStack needs to submit it for you.

Quick Guide

1. 1Create a successful store build first.
2. 2Choose Android or iPhone in Step 5.
3. 3Pick the destination such as Internal testing, Production, or TestFlight.
4. 4Make sure the publish-only setup items for that platform are complete.
5. 5Use Publish this build.

Technical Guide

• Android publish targets: internal, closed, open, production.
• iPhone publish targets: TestFlight or App Store release.
• WholeStack checks project-scoped publish prerequisites before submission starts.
• Android publish requires Google Play service account JSON and first manual upload completed.
• iPhone publish requires App Store Connect app ID and submission credentials.

Quick Guide

• If store build is blocked immediately, confirm you connected your Expo token in Step 1.
• If Android build is blocked, check the Android package name and signing choice.
• If iPhone build is blocked, check the iPhone bundle identifier and signing choice.
• If Android publish is blocked, add the Google Play service account JSON and confirm the first manual upload.
• If iPhone publish is blocked, add the App Store Connect app ID and API key.
• If Expo reports owner or signing failures, verify the Expo owner saved in WholeStack first.

Technical Guide

WholeStack now hides old preview EAS configuration warnings from users. If a store build still fails at EAS level, the most common causes are a missing Expo token, wrong Expo owner, missing project identifiers, missing signing credentials, or missing store submission credentials for the publish step.

Follow this sequence to go from the dashboard to a working app. You can start with a prompt, import a GitHub repo, or begin from a template depending on how much structure you already have.

Step 0: Confirm access and plan

• Free: 20 credits per month and limited preview/build access.
• Pro: 200 credits per month with broader generation/build capacity for recurring app delivery.
• Agency: 800 credits per month plus highest limits and access to Mobile Preview on Web and gated advanced flows.

Step 1: Open dashboard

The dashboard is the best place to begin. You will see your project name field, the app prompt box, your recent projects, and the three main start paths: create with a prompt, use GitHub, or start from a template.

Step 2: Choose how to start

• Start with a prompt when you want WholeStack to build from your description.
• Use GitHub when you already have a repository and want to bring that code into WholeStack.
• Start with a template when you want a polished starter with an existing structure and visual style.

Step 3: Name your project

Use a clear 2-50 character name. A specific name like FitTrack Mobile is easier to recognize later than a generic label like Test App.

Step 4: Start with a prompt

If you choose the prompt flow, describe who the app is for, what it should do, and the main screens or actions you want included. The more specific your prompt is, the better the first version will match your idea.

Build a service booking app for local cleaning businesses with customer onboarding, booking calendar, service package selection, and payment-ready checkout screens.

Build a marketplace app for handcrafted products with seller profiles, product details, favorites, cart, and order history.

Build an internal field operations app with jobs queue, status timeline, visit notes, and offline-friendly updates.

Step 5: Import from GitHub

If you already have a codebase, import it from GitHub instead of starting from scratch. WholeStack will bring the repository into a project workspace so you can keep building inside the platform.

Step 6: Start from a template

Templates are best when you want a ready-made starting point with a real app structure, sample screens, and placeholders already in place. Open the template library, browse or search, review the template details, choose the one that fits your app, then create the project with your own name.

Step 7: Create the project

Click Create Project when your prompt or starter is ready. WholeStack will create the project and open the workspace for you.

Step 8: Understand the project layout

• Left pane: the AI conversation sidebar, where you can switch modes, review history, and send new requests.
• Main pane: workspace tabs for Code, Mobile Preview on Web, Preview on your Phone, and Build and Publish your App.
• Top actions: export and download controls for finished artifacts.

Step 9: Run your first AI Build request

1. 1Select Build mode.
2. 2Ask for one focused improvement or feature.
3. 3Submit and wait for processing to complete.
4. 4Review the response and generated changes.

Step 10: Inspect and adjust code

• Open files with a single click.
• Pin tabs with a double click.
• Use the file menu for New File, New Folder, Rename, or Delete Permanently.

Step 11: Use quick edit (optional)

1. 1Select code in editor.
2. 2Use Quick Edit (Cmd/Ctrl + K from selection tooltip).
3. 3Describe the targeted transformation.
4. 4Review and keep/refine the result.

Step 12: Validate on device (Preview on your Phone)

1. 1Open Preview on your Phone tab.
2. 2Install/open Expo Go from step-1 QR if needed.
3. 3Click Start Phone Preview.
4. 4Wait for queued/starting/running states.
5. 5Scan QR and validate the app behavior.
6. 6Use Copy Link for sharing and Stop when done.

Step 13: Build artifacts (Pro/Agency)

• Open Build and Publish your App.
• Complete the guided setup steps for the platform you want.
• Use Generate Store Build to create the Android AAB or iPhone store build.
• Use Release & Publish later when your store account details are ready.

Step 14: Export source to GitHub

1. 1Click Export in top action bar.
2. 2Set repository name, visibility, and optional description.
3. 3Create repository and follow export status.

Step 15: Continue to deploy/publish

At this point you can continue inside WholeStack with Generate Store Build and Release & Publish, or export your source and handle release work outside the platform if you prefer.

WholeStack works best when you treat each project as an ongoing workflow. You can start from a prompt, import existing code, or use a template, then keep improving the same project over time.

Recommended iteration loop

1. 1Define a small milestone.
2. 2Request scoped AI implementation.
3. 3Review and adjust code manually.
4. 4Validate in phone or web preview.
5. 5Build artifact for that milestone.
6. 6Record known issues and repeat.

When to use each start path

• Use a prompt when you want WholeStack to create the first version from your idea.
• Use GitHub import when you already have code and want to continue inside WholeStack instead of starting over.
• Use a template when you want a polished starter with structure, sample screens, and placeholders already prepared.

Recent projects and continue

• The dashboard shows your most recent project first so you can continue quickly.
• The continue card takes you back into the latest project without making you search for it.
• The full projects list is there when you want to switch work or open something older.

Project management controls

• Recent projects list with a continue card and quick navigation.
• View all opens the project command dialog.
• Delete project action with confirmation dialog.
• Inline project rename from the workspace navbar.
• Save-state indicator tooltip with last update recency.

1) AI Chat (Conversation Sidebar)

AI chat is mode-aware and credit-aware. Build mode handles feature/code requests, while Test and Security modes are available according to plan and feature gates.

• Top controls: mode selector, history button, new conversation button.
• Model selector: Best AI Model or Basic Model, with visible credit cost guidance.
• Status indicators: credit balance and reset date.
• Message controls: per-message mode badge and Copy action on latest assistant output.
• Input behavior: submit, and cancel/stop behavior during active processing.

1. 1Select Build mode for implementation requests.
2. 2Write one scoped request with acceptance criteria.
3. 3Submit and monitor processing state.
4. 4Review output and continue iterating.

2) Template Library

The template library helps you start with a ready-made app instead of a blank page. You can browse the available starters, search for a style or product type, open a template to see its details, and then create your project from that starter.

• Browse the template list to see the available starters.
• Use search to narrow the list to a type of app or feature set.
• Open a template to review its details, screenshots, and included pieces.
• Choose a starter and give the new project a name.
• Create the project and continue from the generated workspace.

3) Live Coding

Live coding shows which path/file is being actively touched during AI processing and can open the active editing file automatically.

• Toggle from editor status row (Live coding switch).
• Observe Now editing path/range while AI is processing.
• Disable when you want stable manual navigation during large refactors.

4) Code Editing and File Explorer

• Root controls: create file, create folder, collapse/reset tree.
• File actions: open, pin, rename, delete.
• Folder actions: expand/collapse, new child file/folder, rename, delete.
• Editor tabs: active tab switching, pin behavior, close via X.
• Breadcrumb path for active file context.

5) Preview on your Phone (Expo Go)

1. 1Open tab and complete Expo Go setup from step 1.
2. 2Go to step 2 and start preview session.
3. 3Scan generated QR and validate behavior.
4. 4Use Copy Link for sharing and Stop when complete.

6) Mobile Preview on Web (Agency + gated)

• Select device preset and orientation.
• Start preview session.
• Use Advanced panel for preview builds and EAS re-init actions.
• Use diagnostics details for preview failures.

7) Build and Publish your App

• Build IOS App and Build Android App actions.
• Quota and subscription state messaging.
• Last Builds list with direct platform download actions.

8) Download Artifacts

Top action bar shows Download APK and Download iOS Build only when corresponding artifacts are ready and feature flags are enabled.

9) Export to GitHub

• Open Export popover from top action bar.
• Set repository name, visibility, and description.
• Track exporting/completed/failed states and retry if needed.

Soon you will be able to deploy directly from WholeStack with just a few clicks, without leaving the platform.

Current deployment is external. WholeStack gets you to stable source/build artifacts, then you continue through your release infrastructure.

Deployment path options

• Path A: Expo/EAS release pipeline (export source, configure release profiles, run release builds).
• Path B: Native release pipeline (Xcode/Android Studio signing, archive, staged rollout).

Example release commands (EAS)

git clone <your-exported-repo>
cd <your-exported-repo>
npm install

# Use release profiles, not preview-only profiles.
eas build --platform android --profile production
eas build --platform ios --profile production

WholeStack can publish directly from your project workspace once you already have a successful retained store build and the publish-only credentials for the target platform are saved.

Open your project, go to Build and Publish your App, and use the Publish step. WholeStack keeps build and submission setup in the same project flow so you do not need to leave the project workspace to start a store submission.

Quick project workflow

1. 1Open the project you want to release.
2. 2Go to Build and Publish your App.
3. 3Confirm Expo access is connected and the project build setup is complete.
4. 4Create a successful retained store build first if you do not already have one.
5. 5Open the Publish step, choose Android or iPhone, select the destination, and submit the retained build.

What must be ready before publishing

• A retained store build must already exist for the platform you want to publish.
• Your Expo token must be connected because WholeStack uses your Expo account for build and submit operations.
• Android publishing requires Google Play service account JSON and confirmation that the first manual Play Console upload is already done.
• iPhone publishing requires the App Store Connect app ID and App Store Connect submission credentials.

How submission works inside the project

• WholeStack validates the project-scoped publish requirements before submission starts.
• The Publish step lets you choose Android tracks such as internal, closed, open, or production, and iPhone destinations such as TestFlight or App Store release.
• WholeStack submits the selected retained build by using your connected Expo account and the project's saved store credentials.
• After submission starts, you can monitor the latest publishing attempt from the same project workflow.

After submission

WholeStack starts and tracks the submission from the project, but store-console work can still be required after the handoff. For example, Apple and Google may still require metadata, compliance answers, review actions, rollout decisions, or final approval steps inside App Store Connect or Google Play Console.

Project creation fails

• Verify project name is 2-50 characters.
• Ensure prompt is not empty.
• Confirm plan project limit has not been reached.

AI message rejected

• Check mode validation requirements.
• Check credit balance and reset timing.
• Confirm mode availability for current plan.

Phone preview not starting

• Confirm Expo setup and session transitions.
• If stale, Stop and Start again.

Build button disabled

• Check plan access and subscription status.
• Check remaining monthly build quota.
• Check if another build is already in progress.

Export to GitHub fails

• Confirm plan entitlement and GitHub account connection.
• Validate repository name and visibility settings.

Artifact

A build output produced for a target platform.

Preview build

Build used for iteration and testing workflows.

Release build

Build intended for deployment and store publishing.

Conversation mode

Behavior policy for AI requests (Build, Test, Security).

Quota cycle

Monthly reset window that governs plan-limited actions.

When product controls change, update this documentation in the same pull request so users always have accurate guidance.

• Document new/changed controls and gating behavior.
• Document failure states and recovery steps.
• Update step-by-step workflows when behavior changes.