# Technical Architecture

## What this guide does

This is the plan for how your app or website works.
Technical just means the parts behind the screens.

Share this guide and the product guide with your AI.
It can explain the choices and help fill them in.
You do not need to know all the answers now.
Ask what each choice means before you choose it.

## Where it runs

- Is this a website, an app, or both?
- Which phones or computers should it work on?
- Which tools will we use to build it? Why do they fit?
- How will I open the first test version?

## The screens

- What code shows each screen?
- How do screens share the same colors, fonts, and buttons?
- Where do the screen words live so we can change or translate them?

## The saved information

- What do we save?
- Does it stay on the device, go online, or both?
- What links the saved parts together?
- Who owns each part? Who can read or change it?
- What happens when a save fails or the internet drops?
- How do we keep saved information when the app closes or gets an update?

Lunchbox example: each week has five lunch choices and belongs to a family. Two approved parents can share the plan, so this version uses online storage. Test that the choices remain after closing and reopening the app, and that another family cannot read them. A version for one person could save on one device instead.

## Login and safety

- Do people need an account? Why?
- How do they sign in and get back in?
- How do they leave and delete their data?
- How do we check that one account cannot get another account's private data?
- Where do secret keys, codes that can act like app passwords, go so they stay out of chats and GitHub?

A public setup key and a secret key have different jobs.
Ask your AI which kind each key is and where it belongs.

## Extra tools

Only include what the app needs:

- Payments: how do we know a payment worked or was refunded?
- AI: where does it run, what can it do, and how do we limit cost?
- Photos and files: who can add or open them, and how large can they be?
- Reminders: when should they arrive, and how does a person turn them off?

## Build and test

Plan the screens early. Set up the saved data and access rules before
connecting the finished screens. Then make one small task work all the way
through. Check it before adding the next task.

- What is the first small task we can make work from start to finish?
- How will we check each part?
- How will we keep test data apart from real data?
- How do we save a version of our work and send it to GitHub? Your tools call these commit and push.
- How do we check the changes before adding them to the main version? Adding them is called a merge.
- Could sending or adding these changes put them online? Make that clear.
- How do we go back if a change breaks something?

## Keep it working

- How will we hear about errors?
- How can a person get help?
- How do we keep an extra copy of saved information and recover it if the original is lost?
- Who will check tool costs and important updates?

## Prompt for my AI

Use this guide and the product guide to explain a build plan for my app.
Show me which parts we need and why.
Use short sentences. Explain any new word. Give the full name of shortened terms, then say what they do in everyday words.
Point out choices we still need to make.
Do not guess, add features, or write code yet.
