Engineering
Why the First-Run Path Is Client → Project → Task — Not a Settings Wizard
Time tracker onboarding usually opens a settings wizard. Theme. Fiscal year. Integration marketplace. Team holiday calendar. A dropdown that wants to know whether you are an agency, a department, or an enterprise before you have a client. That sequence is honest for a product whose first object is a policy. It is a lie for a product whose first object is a clock.
MinuteShark’s first-run path is deliberately boring: add a client, add a project, add a task, start the task. The catalog has to exist before the timer is allowed to mean anything. This post is why we refused the wizard — not a tour of every dashboard widget, and not a rewrite of the getting started checklist a new user actually clicks.
The product bet: a freelancer does not have a configuration problem on day one. They have a naming problem. If the workspace cannot say who the work is for, the play button is a stopwatch with a costume.
Why a settings wizard is the wrong first object
Most time trackers inherit their onboarding from project-management suites. Those products need you to declare a process before they will let you move a card. Freelancers arrive with the opposite hunger: a client already exists, a project already has a nickname, and some slice of work is already happening. Asking them to pick a theme, a default rounding rule, and a notification policy first is how you teach them the product is about compliance.
We also refused the “import your Jira space” first screen. MinuteShark does not market a catalog of native Jira, Slack, Asana, or GitHub integrations. Pretending the first-run path is a sync wizard would be a feature we do not have. Custom development exists for specialized consulting workflows. It is not a self-serve Standard checkbox, and it is not day-one homework.
On the client, MinuteShark is an Ionic + Angular 16 app. Capacitor 7 wraps the same workspace on iOS and Android. Auth, catalog, and time entries live in Firebase. Algolia powers the giant search that can create as well as find. Signup already creates a workspace — a separate digital office with its own client pool. The first-run job after that is not to decorate the office. It is to put one real leaf in the tree so a timer has somewhere to live.
What the first-run path actually is
The hierarchy is load-bearing: Workspace → Client → Project → Task → (subtasks on Standard). Time is tracked on a task. That is not a preference. Entries do not belong to a project folder or a client nickname. If we let you start a timer on “Acme” with no leaf, Friday’s report would have to invent a task you never named. The onboarding copy is the schema, spoken slowly.
Add Client → Add Project → Add Task → Start Task
- Client. A logo you can invoice. Not a Slack channel. Not a Jira project key. One commercial counterpart.
- Project. A named body of work under that client. Tags can wait. The 60-character name limit is a power-user detail, not a first-run sermon.
- Task. The leaf the clock attaches to. Starter already allows unlimited project tasks. Subtasks are a Standard refinement, not a requirement to begin.
- Start. One running timer. Search, the project list, or a confirmed AI card can press play. Nothing writes until the catalog has a place for the minutes.
If you skip a level, you have not saved a click. You have created a blob that reports cannot roll up honestly. Roll-ups are views. The leaf is the write.
Search is how you create, not just find
The dashboard’s giant field — “Search anything or start a task” — is the keyboard-first version of the same path. Type a name that is not there and you get Client / Project / Task badges. That is why Algolia sits under the box: instant results, plus the permission to materialize a missing noun without opening a settings tree. We already wrote the keyboard-first Ionic argument. First-run is the reason that command line exists on day one instead of after you “finish setup.”
MinuteShark AI can speak the same sequence in plain English — onboard client → project → task → log time — but it still proposes a card. The user confirms. The wizard we refused is the one that writes twenty defaults before you have met a client. A confirmation card that creates Contoso, then Website Redesign, then Homepage mockups, is the opposite: short, reversible, and catalog-shaped.
What we left out of first run on purpose
Rounding stays off by default. Cost profiles can wait until you generate an invoice. Teams, custom roles, and project visibility filters are real, and they are not the first screen. Subscription management stays on the web; the iOS and Android apps are the clock, not the cashier. After the catalog has a leaf, an onboarding widget can point at the App Store and Play listings so the same workspace shows up in a pocket. That widget is a reminder that the office already exists. It is not a second wizard.
We did not design first-run for a department that needs SSO-as-default before anyone may type a client name. Primary ICP is freelancers, solo consultants, and tiny teams. Enterprise can include custom branding, application customization, and onboarding as a conversation. It is not the default story, and it is not a reason to hide the play button behind a 12-step policy tour. The features list is where the rest of the product sits once the first task is running.
SOC2 Type II, ISO27001, encryption, backups: the workspace is still cloud-synced. Auth is Google, Apple, or email. None of that belongs in front of “who are you billing.” A surveillance product would open on idle detection and screenshot policy. We are the opposite. The first object is a named leaf, started on purpose.
How we tell if the model is working
- Can a consultant start a real timer in the first session without visiting rounding, taxes, or a marketplace?
- Does the first time entry already know its client, project, and task — or did we let a stopwatch pretend?
- Can the same path be spoken to MinuteShark AI and still wait for Confirm?
- Does the phone show the same workspace after the store links, or did we invent a second catalog?
If the answer depends on finishing a wizard, we shipped a department tool. If the answer is four nouns and a play icon, the first-run path matches how independents already work. Time data should help you think. A settings tour that delays the first honest minute is not thinking. It is homework.