All work

Case study 03

Driving instructor diary

FirstDrive

Driving instructors juggle lessons, pupil progress and the gaps in their diary across separate tools.

The actual website

Try it for yourself.

Explore the actual website. Scroll and click inside the frame.

Open full website

01 The project

What we
built.

A mobile diary built around an instructor’s working week: recurring lessons, existing-pupil invites, syllabus progress, earnings and unfilled gaps. A companion website introduces the app ahead of launch.

Built in

90 days

At a glance

  • Recurring lessons and working hours
  • Pupil invites and syllabus progress
  • Stats, expenses and diary gaps

02 In practice

Inside the product.

Follow the experience from first step to outcome. These interactive illustrations use example data.

Explore FirstDrive
For the independent instructor

Your pupils.
Your working week.

Bring existing pupils into one place through an invite or code.

Instructor
Bring your existing pupils
Keep teaching personal.

An instructor workspace for the diary, pupils, stats and gaps.

Illustrative walkthrough. Example data.

1 of 3

Bring your pupils together

Existing pupils join through an invite or code, connecting their learning to the instructor’s working week.

03 Design & engineering

Behind the build.

The decisions, the working parts and what connects them.

The diary is the centre of FirstDrive. Instructors set their working hours, invite the pupils they already teach and organise recurring lessons, keeping the week together instead of rebuilding it across messages and separate calendars.

Pupil records bring lesson history and syllabus progress into the same place. Stats and expense exports help with the business side, while the gaps view makes unfilled time visible. The companion pupil app gives invited learners a way to stay connected to their instructor.

The mobile experience is built with React Native and Expo, with a Next.js companion website and Supabase behind the product. The first release focuses on instructors and their existing pupils, with marketplace discovery planned for a later phase.

The working parts.

How the build is organised.

  1. App

    • Instructor diary
    • Pupil companion
  2. Product

    • Recurring lessons
    • Pupil progress
    • Stats & gaps
  3. Platform

    • React Native / Expo
    • Next.js
    • Supabase

Built with

  • React Native (Expo)
  • Next.js
  • Supabase

For a similar project

The decisions
that matter.

Start with the working relationship instructors already have. Existing-pupil invitations and recurring lessons make the diary useful without requiring a marketplace of new learners on day one. Pupil progress and the instructor’s business records sit alongside that weekly routine.

The first release is being prepared for launch, with marketplace discovery planned later. That boundary matters for a new app: a useful first release can serve an existing customer base before introducing the separate challenge of matching supply and demand.

Plan a connected software product

By Alwan Technologies · Updated

Have a project like this in mind?