After creating a Hi-fidelity design that I made through Figma then I made a prototype through the Marvel App. I did a test to validate the main pain points. As a target of the success of the flow that I made that aims to make it easier for users to repair damaged phones. I tested 5 people who were interviewed before to try the results that I made.
Here my goals for this design are functional and user-friendly
Feedback from Participant
- The application is very easy and simple to use, the stages are quite clear and do not take much time
- I really like the choice of purple and orange is very suitable
- Information about the response hasn’t been made so I can’t see other people’s comments about the store
- Need to add a map feature that is connected with Google / Maps app
From the results of the validation that has been done, the design created makes it easy for users. But I still have a lot to develop and improve in terms of UX as well as UI. As I know when this design thinking has been formed it doesn’t just stop until the implementation but there must be an evaluation for the development of this application.
Service-In was actually formed from a problem that I faced with my iPhone 7 compilation broken. I was confused about what to look for and had to spend more effort to find out the store, find the right price, etc.
“Don’t stare at a blank page for too long, be bold, and make the first incisive stroke. The rest will come naturally.” — James Kingman
Then I wondered why I didn’t make a service application that made it easy for people when their cellphones broke. As far as I know there is no benchmark on this issue.
I thought at that time I would make a simple Service-In application like services in a Gojek application like go-life, go-tix, etc. Maybe someday will Gojek can make go-fix that serves as well as Service-In
In this case there is also one Idea that has not yet been realized, namely the ordering feature where the gadget technician comes to the user’s home