> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/start-or-join.md).

# Start or join

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/onboarding/start-or-join.md).
{% endhint %}

Someone signed in without a site chooses to start a new company or team in Snapfix, or to say they are joining one that already uses it. This is step 1 of the app's setup flow.

* **Where:** iOS and Android, after sign-in, sign-up or app launch, when the stored flag `should_create_business` (Android `shouldCreateBusiness`) is 1. Android also checks it on the splash screen, the walkthrough, a deep link and SSO sign-in.
* **Who:** in the current code, nobody reaches it. Every iOS sign-in path reads the server's value and stores 0 (`should_create_business = 0 //value`) \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)]. On Android, password and code sign-in store "0", and SSO and registration store the user's value, but its getter always returns "0", with the comment "Removed Onboarding flow for now" (android @ 86068bfeea, `model/User.java:613-617`). So the setup flow (this screen to [Configuring Snapfix](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/configuring.md)) only opens for a flag of 1 left on the phone by an older app version \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)]. The rest of this area describes what the screens do when they are reached.
* **Feature:** [Site setup in the app](https://docs.snapfix.com/product/features/onboarding/site-setup.md). The invitation route into a site is in [Joining a site](https://docs.snapfix.com/product/features/onboarding/join-site.md).

Both choices end in the same kind of create-site call; only what is sent differs. Starting goes on to [Work types](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/work-types.md), which become starter groups. Joining skips work types and [Let us help you](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/let-us-help.md) and sends the note "joining a company" ([Configuring Snapfix](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/configuring.md)).

## Layout

1. The Snapfix logo. Android puts it in a top bar with a back arrow at the left; iOS has no back control on this step.
2. A progress bar: Android sets it to 20; iOS's bar is fixed at 0.15 in the layout. Android's step counter text ("1/5") is in a frame that the layout hides, so it never shows.
3. The greeting "Hi ,\nWelcome to Snapfix." iOS takes it from the localized string `hi_welcome_to_snapfix` with the saved user's first name. Android builds "Hi " + the saved name + ", \nWelcome to Snapfix." in code, in English only.
4. "What would you like to do?"
5. Two cards:

| Card  | Title                                    | Detail on iOS                                                             | Detail on Android                                                             |
| ----- | ---------------------------------------- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Start | "Start a New Company or Team in Snapfix" | "I’m registering a new company or team to see it done."                   | "I’m registering a new company or team to Get things done."                   |
| Join  | "Join a Company or Team"                 | "I’m joining a team or company that already uses Snapfix to see it done." | "I’m joining a team or company that already uses Snapfix to Get things done." |

The detail lines differ between the apps for no clear reason.

6. "Next", disabled until a card is picked.

## Inputs

| Field         | Type             | Required | Default | Rules and messages                                                                                         |
| ------------- | ---------------- | -------- | ------- | ---------------------------------------------------------------------------------------------------------- |
| Start or join | One of two cards | Yes      | None    | Tapping a card highlights it; tapping the other moves the highlight. "Next" is enabled once one is picked. |

## Actions

| Action               | Who                  | What happens                                                                                                                                                               | API  |
| -------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- |
| Tap a card           | Anyone on the screen | Picks the card and enables "Next". iOS stores `startCompany` or `joinCompany` in the shared setup parameters; Android keeps a join flag. Each tap logs an analytics event. | None |
| "Next"               | Anyone, after a pick | Opens [Company and role](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/company-and-role.md) for both choices; the choice changes the steps after it.       | None |
| Back arrow (Android) | Anyone               | Visible on first open, because the activity starts on step 1 without hiding it. It leaves the setup screen. Coming back to this step from the next one hides it.           | None |

## States

* **Loading:** none. The screen makes no calls.
* **Empty:** no pick yet; "Next" is disabled.
* **Error:** none.
* **No permission:** only the stored flag above opens the flow. The screen has no role check.
* **Offline (mobile):** works. The next step loads the industries and needs a connection.

## Dialogs and sheets

None.

## Platform differences

| Topic       | iOS                     | Android                                |
| ----------- | ----------------------- | -------------------------------------- |
| Greeting    | Localized string        | Built in English in code               |
| Card detail | "…to see it done."      | "…to Get things done."                 |
| Progress    | Bar at 0.15, no counter | Bar at 20; the "n/5" counter is hidden |
| Back        | None on this step       | Arrow visible on first open            |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/onboarding/start-or-join.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
