Problem
Finding a tutor lived in scattered groups, with no clear request path.

Case study
An education platform connecting students and teachers: search, requests, and tutoring offers.

From Google Play


Finding a tutor lived in scattered groups, with no clear request path.
A two-sided product to search, submit requests, and offer support lessons.
Flutter · Backend APIs · Authentication
Teacher profiles · Student requests · Tutoring offers · Two-sided accounts
Serve both sides in v1 without bloating the marketplace.
Tutoring as a product journey, not a group post.
A clear request beats a long directory.
Connection first; scheduling/payments if they create trust.
Two distinct paths: student / teacher.
A mobile platform with roles for student and teacher.
Flutter with accounts and roles.
Users, requests, offers.
Not the launch core. Smarter matching only if it actually improves connection.
Create a request and answer it.
Google Play as a live education platform.
Matching and session flow from real use.
Result
Live on Google Play as BritiDirSwaye3.