# AppBento · Example launch plan

**Illustrative sample for the fictional Table Note app.** This is a discussion
document, not a customer case study, a runnable code package, an accepted quote,
or a record of completed native/payment verification.

## 1. First user flow

Unlock a nutrition report → ask a contextual question → inspect reply usage →
reread the owned report, including when no replies remain.

Optional memory extension: correct saved prep time from 15 to 10 minutes and
generate a different meal. Earlier answers remain available.

Modules: Interactive Reports, Native AI Chat, Editable Memory, Membership & Usage.
The combination illustrates this example; your app can use a smaller selection.

## 2. Proposed scope to agree

- One report type and its chapter-based follow-up flow.
- A native conversation with streaming, stop, error and retry states.
- View, edit, pause and remove the agreed preference records.
- Explicit report ownership and reply-allowance rules.
- Source code and integration within the agreed project/platform scope.
- Setup notes, acceptance steps, handover and agreed support terms.

Before work: review existing React Native code; confirm iOS/Android targets,
backend/model and billing providers, product identifiers, data storage/deletion,
purchase restoration/refund rules, concurrency and expiry behavior. Confirm
licensing, revision rounds, support duration, timing and a written quote.

AI usage, hosting, store accounts, taxes and third-party fees are separate.
Store approval and revenue are not guaranteed.

## 3. Example source organization

This is an illustrative file outline, not a downloadable implementation.
Actual project structure is agreed after reviewing your app.

| Location | Responsibility |
| --- | --- |
| `src/reports/` | Report screens, chapter structure and source context |
| `src/chat/` | Conversation, reply lifecycle and contextual follow-ups |
| `src/memory/` | View, correct, pause and remove preferences |
| `src/access/` | Ownership, membership and usage rules |
| `docs/setup.md` | Installation, local run and configuration |
| `docs/acceptance.md` | Agreed flow, expected behavior and verification record |

## 4. What setup notes should contain

1. Supported runtime, package manager and exact installation/run commands.
2. Required provider and store accounts; configuration names without secrets.
3. How to run locally and on the agreed target devices.
4. How to configure products, entitlements and the chosen AI provider.
5. How to replace sample content and branding.
6. Known limits, troubleshooting and handover contact.

Commands and provider-specific steps belong to the actual agreed project;
this example does not invent a runtime or imply those integrations exist.

## 5. Example acceptance criteria

These checks must be agreed and executed against the delivered project.
Unchecked items below do not imply successful acceptance.

- [ ] Unlock a report and ask about its chapter. The reply includes report
  context; completion consumes one reply credit.
- [ ] Change prep time from 15 to 10 minutes. The next meal, ingredients and
  method change; the earlier reply and its preference snapshot remain intact.
- [ ] Stop or fail a reply. Remaining credits do not decrease. Complete a
  retry: exactly one credit is used for the completed reply.
- [ ] Exhaust the reply allowance. New replies are blocked, while the owned
  report and existing conversation remain readable.
- [ ] Edit or remove a preference. Future suggestions respect the change;
  earlier content is preserved and the agreed deletion policy is verified.
- [ ] Run on the agreed target platforms and exercise the agreed store,
  restore, refund, concurrency and expiry paths with the real integrations.

## 6. Your next step

Email **support@usefulmint.com** with your current prototype and the first user
flow you want to complete. We clarify the scope by email, then agree the modules,
deliverables, acceptance criteria, quote and support terms before work begins.