EM PH Contact

Job posted · 2026

Post a job. Pick who you want. Get it done.

A two-sided marketplace that connects people who need work done with people ready to do it — designed end to end for both sides.

The job
Design a two-sided marketplace, end to end
Platform
Mobile app
Duration
4 weeks
Skills
UX Research · UI/UX Design · Prototyping

Krishom SharmaSole designer — UX research, UX and UI design, and the interactive prototype.Approved ✓

WorkMaster X dashboard: total balance, jobs applied and approved, and latest posts

The job board · 4 weeks

Watch this project move through the app’s own lifecycle.

  1. PostedBrief

    The job is posted

    WorkMaster X is a two-sided marketplace. Someone posts a task — say, help moving to a new room — providers apply, and the poster chooses whoever they prefer. Two-sided marketplaces are hard: posters and providers each need flows that feel obvious. Posting a job, reviewing applicants and tracking work in progress all had to feel effortless on a small screen.

  2. AppliedWeek 1

    Two sides, one market

    Who posts work, who does it, and what each of them needs to feel sure enough to tap “post” or “apply”.

  3. ApprovedWeek 2

    Map both journeys

    Posting a job and applying for one, mapped into clear paths — and a lifecycle with obvious states, so both sides always know what happens next.

  4. In progressWeek 3

    Design the screens

    A clean, friendly interface that keeps a genuinely complex marketplace simple to pick up — sign in, dashboard, job detail, posting, chat, profile.

  5. DoneWeek 4

    Prototype and refine

    An interactive prototype, used to test and refine the experience before build.

Two journeys, one app

Pick a side.

  1. 1
    WorkMaster X — Post the job
    Post the job
  2. 2
    WorkMaster X — Fill in the details
    Fill in the details
  3. 3
    WorkMaster X — Published
    Published
  4. 4
    WorkMaster X — Talk to applicants
    Talk to applicants
  1. 1
    WorkMaster X — Find work
    Find work
  2. 2
    WorkMaster X — Read the job
    Read the job
  3. 3
    WorkMaster X — Apply
    Apply
  4. 4
    WorkMaster X — Hear back
    Hear back

Every screen · 13

From sign-in to the last message.

  • WorkMaster X — Login
    Login
  • WorkMaster X — OTP
    OTP
  • WorkMaster X — Dashboard
    Dashboard
  • WorkMaster X — Home
    Home
  • WorkMaster X — All tags view
    All tags view
  • WorkMaster X — Job detail
    Job detail
  • WorkMaster X — Applied
    Applied
  • WorkMaster X — Job posting
    Job posting
  • WorkMaster X — Job posting filled
    Job posting filled
  • WorkMaster X — Job published
    Job published
  • WorkMaster X — Chat
    Chat
  • WorkMaster X — Notification
    Notification
  • WorkMaster X — Profile
    Profile

The UX work

Behind the design

  • From the build — read off the real screens
  • Assumption — to validate with users
  • Planned test

From the build

  1. 01

    Sign-in is a phone number and a four-digit OTP — no password, no email.

    WhyMany providers live on their phone, not their inbox; every extra field is a reason not to start.

    Login · Verify number

  2. 02

    The home screen groups your work by state: Job Applied, Job Approved, Job In Progress.

    WhyIn a two-sided market the anxious question is “where does it stand?” — the lifecycle is the navigation.

    Home

  3. 03

    The hourly price leads every job card, and on the job page it stays pinned beside Apply Now.

    WhyPay is the deciding fact for a provider; it should never scroll out of view at the moment of deciding.

    Latest Posts · Job detail

  4. 04

    Posting a job is one screen of chips: dates, time slots, tags and requirements are tapped, not typed — with “Create own requirement” for the rest.

    WhyTyping is the slowest thing on a phone; structured chips also give providers jobs they can compare.

    Post Job

  5. 05

    Limits are shown before they bite: 0/50 for the title, 0/500 for the description, 2/5 photos.

    WhyPeople write to the space they are given; showing it prevents errors on submit.

    Post Job

  6. 06

    Every commitment ends in a confirmation with one next step — “Job Published”, “Applied Successfully”, each with Let’s Go.

    WhyClosure plus a clear next move removes the “did that work?” moment.

    Job Published · Applied

  7. 07

    Language and Dark Mode sit in the profile, not buried in settings.

    WhyA local marketplace serves a broad audience; both affect whether the app is usable at all.

    My Profile

Assumption — to validate · The poster, getting a house shifted

Stage1Notice the need2Post the job3Wait4Choose5Get it done
DoingRealises the move is this weekendAdds title, description, address, date, time, photos and tagsChecks back for applicantsCompares applicants and messages oneTracks the job until it is finished
Thinking“Who do I even ask?”“Have I said enough for people to apply?”“Has anyone seen it?”“Can I trust this person?”“Is it on track?”
Feeling
uneasyneutraluneasyneutralpositive
PainWord of mouth is slow and hit-and-missLong free-text forms on a phoneSilence after postingToo little to compare people onNot knowing where things stand
Design response“Find the best service provider” — Post Job on the home screenChips for dates, time slots, tags and requirements; visible limits“Job Published — watch out for applicants in a few mins”, then notificationsA rating on every post; chat before committingApplied → Approved → In progress, visible on the home screen

Proto-personas — built from the brief, not from interviews

  • The poster

    A busy local who needs something done this week — moving house, walking the dog

    Wants
    Find someone reliable at a fair hourly rate without phoning around
    Frustrated by
    No way to tell who is trustworthy; prices vary wildly

  • The provider

    A local worker or student taking on tasks by the hour

    Wants
    Steady work nearby, with the pay clear up front
    Frustrated by
    Vague job posts, and never hearing back after applying

From the build — the information architecture as shipped

  • Sign in
    • Phone number (+91)
    • Verify number (OTP)
  • Home
    • Search & filter
    • Post Job
    • Job Applied
    • Job Approved
    • Job In Progress
    • Latest Posts
  • Dashboard
    • Total balance
    • Jobs applied
    • Jobs approved
    • Applicant requests
  • Jobs
    • Tags — Pet Care, Shifting, Cars, Home, Party
    • Job detail
    • Apply
  • Post a job
    • Title & description
    • Address
    • Date & time
    • Photos
    • Tags
    • Requirements
  • Messages
    • Conversations
    • Swipe to delete
  • Notifications
    • Today
    • Yesterday
  • Profile
    • Edit Profile
    • Privacy & Security
    • My Bookings
    • My Addresses
    • Dark Mode
    • Notifications
    • Language
    • Policies
    • Logout

From the build — key flows, screen by screen

Posting work

  1. 1Home
  2. 2Post Job
  3. 3Fill in the details
  4. 4Job Published
  5. 5Messages

Doing it

  1. 1Verify number
  2. 2Home
  3. 3Select tags
  4. 4Job detail
  5. 5Apply Now
  6. 6Applied Successfully

The validation plan — how each assumption gets checked

  1. We believeA poster can publish a complete job in under two minutes.

    MethodModerated usability test, 5 people who have hired help locally

    We’ll know byTime on task; fields left empty; errors

  2. We believeProviders can tell, from the home screen alone, which of their jobs are approved.

    Method5-second test + follow-up question

    We’ll know byShare who identify the approved job correctly

  3. We believeA pinned price beside Apply makes the decision faster than a price in the description.

    MethodFirst-click test on two versions of the job page

    We’ll know byTime to first click on Apply; confidence rating

✓ Done

Job complete.

Both sides designed end to end — posting, applying, approving and tracking — in an interactive prototype.

  • UX Research
  • UI/UX Design
  • Prototyping
Post me your next job →