eBakja - mobile application for parents to pay kindergarten fee & tracking their children’ food, education, daily schedule.
eBakja - mobile application for parents to pay kindergarten fee & tracking their children’ food, education, daily schedule.
Collaboration with Ministry of education of Turkmenistan
Collaboration with Ministry of education of Turkmenistan
My Role
My Role
In my role designing for eBakja, I focused on the User Experience (UX) and User Interface (UI), ensuring problem solving app for parents. My responsibilities included:
In my role designing for eBakja, I focused on the User Experience (UX) and User Interface (UI), ensuring problem solving app for parents. My responsibilities included:
Research and Insights
Planning and Ideations
Building project vision
User Interface & Experience
Research and Insights
Planning and Ideations
Building project vision
User Interface & Experience
Main Problem in our users
Main Problem in our users
Most parents forget to pay kindergarten fee every month.
Some parents don’t go to the kindergarten by themselves, they sent their children by their drivers and giving kindergarten cash payment from them.
Most parents forget to pay kindergarten fee every month.
Some parents don’t go to the kindergarten by themselves, they sent their children by their drivers and giving kindergarten cash payment from them.
My task by Stakeholder’s perspective
My task by Stakeholder’s perspective
Stakeholders only wanted the “Payment feature” for kindergarten paying
Stakeholders only wanted the “Payment feature” for kindergarten paying
They initially believed that implementing a payment feature for kindergarten would suffice. However, they overlooked a critical issue: parents, who might only use the app for occasional fee payments, such as once every three months or monthly, wouldn't engage with the app regularly.
They initially believed that implementing a payment feature for kindergarten would suffice. However, they overlooked a critical issue: parents, who might only use the app for occasional fee payments, such as once every three months or monthly, wouldn't engage with the app regularly.
So I started Researching the project
So I started Researching the project
How we can keep users in the app, what kind of benefits we can give them. I took user interviews to get insights and define problems, I talked with:
Young families age around 25-35
Families that have 2-5 years old children
Kindergarten teachers
How we can keep users in the app, what kind of benefits we can give them. I took user interviews to get insights and define problems, I talked with:
Young families age around 25-35
Families that have 2-5 years old children
Kindergarten teachers
We brainstormed features that can solve users’ problems, and set meeting with developers and stakeholders. Discussed on two things:
We brainstormed features that can solve users’ problems, and set meeting with developers and stakeholders. Discussed on two things:
01
By the budget and time of stakeholders, can we solve users’ problems with possible features
By the budget and time of stakeholders, can we solve users’ problems with possible features
02
Technical Limitations of developers
Technical Limitations of developers
The big challenge for me is I started building the information architecture on my own without testing. During the project, I suggested a UX Researcher who suggested using card sorting results to build the architecture. We tested it with 8 people, and the results were totally different from what I first thought.
The big challenge for me is I started building the information architecture on my own without testing. During the project, I suggested a UX Researcher who suggested using card sorting results to build the architecture. We tested it with 8 people, and the results were totally different from what I first thought.
At first, I was really surprised and a bit stressed about having to redo wireframes and architecture after spending days on them. But after seeing what we learned from the card sorting, I knew it was the right move. Working with the UX researcher opened my eyes to new ideas, and even though it meant starting over, it turned out to be a great learning experience
At first, I was really surprised and a bit stressed about having to redo wireframes and architecture after spending days on them. But after seeing what we learned from the card sorting, I knew it was the right move. Working with the UX researcher opened my eyes to new ideas, and even though it meant starting over, it turned out to be a great learning experience
Card Sorting Process
Card Sorting Process
The Real Design Process
The Real Design Process
I tried a bunch of things to make the app user-friendly:
I talked with real users, interviewed them
Defined problems and ideated possible features
Ensured business side of project and learned tech limitations
Card sorting with users and building information architecture
Creating user-flows making low fidelity wireframes to communicate with stakeholder and developers
Designed app and prototyped flows with figma
User testing of flows with prototypes
I tried a bunch of things to make the app user-friendly:
I talked with real users, interviewed them
Defined problems and ideated possible features
Ensured business side of project and learned tech limitations
Card sorting with users and building information architecture
Creating user-flows making low fidelity wireframes to communicate with stakeholder and developers
Designed app and prototyped flows with figma
User testing of flows with prototypes
Some UI Screens
Prototyping the flows
User testing
User testing
Main payment flow I designed is failed. I analyzed it through user-testing:
Main payment flow I designed is failed. I analyzed it through user-testing:
Tested with 6 people and 5 of them failed. Not understanding design, wrong information architecture
As result I saw user’s mental model is very different from us designers. While I was designing that flow I thought it easy but the testing showed that vice versa.
As result I saw user’s mental model is very different from us designers. While I was designing that flow I thought it easy but the testing showed that vice versa.
I made one solution and tested again same people additionally +3 more people
I made one solution and tested again same people additionally +3 more people
Failed version of Payment Flow
Failed version of Payment Flow
In first screen User can’t select children, these card only representative for status of payment or upcoming payment. Second screen user needs to select the payment then user needs to select which child wants to pay.
In first screen User can’t select children, these card only representative for status of payment or upcoming payment. Second screen user needs to select the payment then user needs to select which child wants to pay.
After User testing
After User testing
After testing I made cards selectable and user needs to select which child it pay first then select payment type
After testing I made cards selectable and user needs to select which child it pay first then select payment type
Conclusion
Conclusion
The project went very well. We're testing it with two kindergartens and some parents now. I enjoyed the design process, and it was successful. It gave me a lot of confidence to build new features and suggest ideas. After I presented these ideas, the stakeholders were impressed and decided to invest more money into the project.
The project went very well. We're testing it with two kindergartens and some parents now. I enjoyed the design process, and it was successful. It gave me a lot of confidence to build new features and suggest ideas. After I presented these ideas, the stakeholders were impressed and decided to invest more money into the project.
Design Toolkit
Design Toolkit
Design Process of Project
Design Process of Project
Contact me
© 2024 • Islam Yuldashev