Overview
Goal
Create a streamlined, intuitive, and engaging experience that minimizes drop-offs, ensures accurate data collection, and sets vendors up for success in using the platform.
Process
Outline what information is needed when signing up
Group similar information
Sketch out screens needed
Outline a few different flows for these screens
Lo-fi wireframes
Scrappy usability test
Test the different flows with 2 users varying in age to gather feedback and pinpoint confusion
Iterate based on feedback
Hi-fi design
Finalize UI elements and get screens ready for development
Design Challenges
1 - Ensuring ease of use for the vendor persona.
Solutions:
- Break up into steps that clearly tell the user what to do
2 - Collecting all necessary information without overwhelming the user.
Solutions:
- Separate signing up for the app and signing up for Stripe
- Group and categorize different pieces of information
Background
What is MyHome?
MyHome gives homeowners the ability to post jobs they need done around their house on the homeowner-facing app, and have those jobs seen by professionals in their area on the vendor-facing app.
Vendors are able to view jobs and send offers to the homeowner who posted it. The homeowner is then notified, can accept or deny the offer, and schedule an appointment with the vendor for the job needed.
Initial Flowchart & Sketches
Lo-Fi for Testing
2 flows were used for scrappy testing.
My goal for this quick test was:
1 - Does it matter when we ask for certain information?
2 - Does breaking up setting up profile and telling us about their business make a difference?
3 - Do users want to see an overview of their info prior to finishing the sign up process?
Results:
- Flow A feels more concise and natural.
- There's no need to break it up in the middle, instead let's give a quick overview after a user has input their email and password.
FLOW A:
FLOW B:
Final Design
