WEEK 5 JOURNEY

Designing the Prototype of Busina: A Bus Tracking and Monitoring App

Because prototypes are built on so much other information, it’s important to gather the necessary details in advance. Consider the following: What are the goals of the project? What competitive products do people currently use? Who is the audience? What are their goals? What type of product is it, and what (device) is it for? Are there any visual precedents to follow? 


Prototyping is a critical step in the development of any app, and Busina is no exception. The design of the Busina prototype was focused on simplicity and ease of use, while still incorporating all of the essential features and functionalities required for bus tracking and monitoring. The prototype was tested with a select group of bus company representatives to gather feedback and refine the design.



Image1. The Figma of Busina App

The process of prototyping—from creating simple wireframes to testing fully functional mockups—is one of the most potent and powerful set of skills any designer can master. Building a prototype is not enough; we have to understand the process involved with constructing a product’s initial drafts. 


The team discuss about the design of the app in all aspects in the front end and especially in the backend of the application prototype. The discussion went well and meet the standards of each member of the team. That's a great 1st step in developing the prototype.


That practical explanation of how something works has a number of high-value benefits, including:

  • Making it real – Before any prototypes are built, the product is completely conceptual! That’s fine for a little while, but eventually it must become something that stakeholders and users eventually understand and appreciate. A prototype is the first step in moving from conceptual to actual.
  • Work a problem – Sometimes, we have a design challenge without a solution. As a skill, prototyping is a great way to visualize the problem and introduce solutions quickly. If it doesn’t work, throw out the prototype and try again.
  • Iterate – Prototyping comes in stages, but the result is the same: to evolve your ideas. From sketches to hi-fis, each new iteration offers a plethora of behaviors and functions to test. And with more data, we can iterate both faster and smarter.
  • Detect unintended scenarios – Once something is visible, we have the limitations of our product available for study, which also provides better context on what should be there…and what shouldn’t!
  • Detect usability problems – This is where many designers live: Once a product has a prototype of any kind, usability challenges suddenly become easy to spot and fix.
  • Presentation – Prototypes at any stage are a standard for presentation. Whether you’re testing a version of a page or presenting a product to a client, a prototype in some form should be there. And if it isn’t, you can bet that someone will ask where it is and why it wasn’t included.
https://www.toptal.com/designers/prototyping/guide-to-prototype-design

Comments

Popular posts from this blog

My Berkeley Innovation Index Result

WEEK 6 JOURNEY