Appearance
Screens
Everything a person can do in the Instagram Android app, screen by screen. Each page below says what the person sees, what you do, and gives a program for each thing you can do on that screen.
How a screen page is laid out
- What the person sees, with a screenshot of the screen.
- What you do: the screen classes the page covers and what their actions are.
- The setup: the imports and the stored session every example starts from.
- The matrix: one row for each thing a person does, with the screen it starts on, the action and the result.
- The scenarios: one for each row, in the same order. Each says what the person does, shows the screenshot where one fits, gives the program, and says what you get.
- What this screen does not offer, where a reader would expect something the app has but the Simulator has no action for.
The shared setup
Every example starts from session.json, the session Your first program saved, and names the screen it expects (screen: FeedTimelineScreen). The examples show the success path: errors are answered as in Errors, and challenges by your otherwise constant (Challenges).
A handle, data and raw, back() and the screen in focus are explained once, in Work with screens.
The screen map
You reach a screen through an action of the screen before it.