2022
Mobile B2B application for cargo transportation
Mobile B2B application
for cargo transportation
for cargo transportation
MVP for
a startup
a startup
It was necessary to create two interconnected applications: one for the customer to find truck drivers, and another for carriers transporting agricultural products. It was also necessary to create a landing page and marketing presentations.
MY TASKS
IN A STARTUP
IN A STARTUP
In a fairly tight timeframe, we had to develop two apps from sketches to finished apps and publish them in the Google Play. As the sole designer on the team, I led the design process, which included:
- conducting UX research
- developing application concepts and create mockups
- presenting to stakeholders
- developing a design system
- collaborating with developers
- participate in testing
Research
Audit & requirements. We started by clarifying the customer’s goals—defining the minimum functionality for the apps and identifying key success metrics.
Competitor analysis. Together with the project manager, we benchmarked over 20 apps and websites with similar functionality, including solutions from the agricultural sector.
Audience research. Through user interviews and surveys, we explored needs, behaviors, and pain points. We learned about a truck driver’s typical workday, challenges during loading, communication patterns with customers, devices and tools they use, and which of their needs are not met by existing products.
Hypotheses. Based on these insights, we worked with the client to define MVP features and document hypotheses—for example, that poor Internet access at loading sites requires offline functionality, or that customers would accept multi-carrier delivery. The entire set of features for the MVP was defined, and extra features were added to the backlog.
Competitor analysis. Together with the project manager, we benchmarked over 20 apps and websites with similar functionality, including solutions from the agricultural sector.
Audience research. Through user interviews and surveys, we explored needs, behaviors, and pain points. We learned about a truck driver’s typical workday, challenges during loading, communication patterns with customers, devices and tools they use, and which of their needs are not met by existing products.
Hypotheses. Based on these insights, we worked with the client to define MVP features and document hypotheses—for example, that poor Internet access at loading sites requires offline functionality, or that customers would accept multi-carrier delivery. The entire set of features for the MVP was defined, and extra features were added to the backlog.
Research
Audit & requirements. We started by clarifying the customer’s goals—defining the minimum functionality for the apps and identifying key success metrics.
Competitor analysis. Together with the project manager, we benchmarked over 20 apps and websites with similar functionality, including solutions from the agricultural sector.
Audience research. Through user interviews and surveys, we explored needs, behaviors, and pain points. We learned about a truck driver’s typical workday, challenges during loading, communication patterns with customers, devices and tools they use, and which of their needs are not met by existing products.
Hypotheses. Based on these insights, we worked with the client to define MVP features and document hypotheses—for example, that poor Internet access at loading sites requires offline functionality, or that customers would accept multi-carrier delivery. The entire set of features for the MVP was defined, and extra features were added to the backlog.
Competitor analysis. Together with the project manager, we benchmarked over 20 apps and websites with similar functionality, including solutions from the agricultural sector.
Audience research. Through user interviews and surveys, we explored needs, behaviors, and pain points. We learned about a truck driver’s typical workday, challenges during loading, communication patterns with customers, devices and tools they use, and which of their needs are not met by existing products.
Hypotheses. Based on these insights, we worked with the client to define MVP features and document hypotheses—for example, that poor Internet access at loading sites requires offline functionality, or that customers would accept multi-carrier delivery. The entire set of features for the MVP was defined, and extra features were added to the backlog.
I created a CJM to structure the information I received and to better understand what screens and functions would be needed and what data would need to be displayed.
UX design
It was necessary to think through the structure and navigation of both applications and make several levels of screens without making the application too “deep”. For the convenience of development, we made similar logic for both applications (for example, both have three key pages: a list of orders, an order in progress, and a personal account)
UX design
It was necessary to think through the structure and navigation of both applications and make several levels of screens without making the application too “deep”. For the convenience of development, we made similar logic for both applications (for example, both have three key pages: a list of orders, an order in progress, and a personal account)
Based on this structure, we developed a content structure to understand what data should be on each screen and in the block (cargo type and weight, loading and delivery address, etc.), and based on this, we created wireframes for both applications.
Based on this structure, we developed a content structure to understand what data should be on each screen and in the block (cargo type and weight, loading and delivery address, etc.), and based on this, we created wireframes for both applications.
Ui design
Next, we moved on to working out each screen. First, we had to approve the UI-design concept. There was a requirement to prepare a dark theme first (this is related to the typical driver's work mode), so I provided several style options for the application in a dark theme. After the customer approved the UI, we began working hard on each screen, selecting colors, working out components, and developing a design system.
Ui design
Next, we moved on to working out each screen. First, we had to approve the UI-design concept. There was a requirement to prepare a dark theme first (this is related to the typical driver's work mode), so I provided several style options for the application in a dark theme. After the customer approved the UI, we began working hard on each screen, selecting colors, working out components, and developing a design system.
design handoff to development and testing
This stage was carried out in parallel with the finalization of the UI of the following screens. At every step I collaborated with developers to ensure the implementation of designed interfaces. Also, simultaneously with these processes, there was testing. I gained experience in testing, learned to prepare test cases and checklists, and compile bug reports.
design handoff to development and testing
This stage was carried out in parallel with the finalization of the UI of the following screens. At every step I collaborated with developers to ensure the implementation of designed interfaces. Also, simultaneously with these processes, there was testing. I gained experience in testing, learned to prepare test cases and checklists, and compile bug reports.
Improvements and Publishing in the Google play
Six months after we started working on the product, we published the application in the store and set up metrics for Firefox.
Improvements and Publishing in the Google play
Six months after we started working on the product, we published the application in the store and set up metrics for Firefox.
We also improved all notifications and created actions for Firefox.
Results
- Conducting various UX studies
- Developing application concepts, creating mockups
- Developing a design system
- Design handoff to development
- Testing
- Successful publication in the Google Store