Challenge Summary
Welcome to the MYTE Mobile App Wireframe Challenge! In this challenge, we are looking to conceptualize the first vision for a mobile application that will integrate all available ground transportation options and allow users to locate, compare, and purchase the most efficient and desirable path to their destination. In addition, the app will include public transit options and set the ground work for a universal public transportation card.
We are looking for an intuitive and easy to use "wireframe concepts" that will let us design and build the final mobile user interfaces on the next stage of this project. Think about what are the best UI/UX practices when creating this wireframe.
2. Social Login
4. Introductions
5. Search
6. Location Based Services
8. Dashboard
11. Marketplace
12. Ratings & Reviews
14. Product Listing
15. Activity Feed
16. Admin Tool
18. Reporting
The objective of this project is to create an application that will integrate all ground transportation services and build the most efficient and seamless way to travel under 50 miles.
Example of ground transportation services is Uber, Lyft, Grab, VIA, Lime, charter buses like Greyhound and Mega Bus, and other local transit options.
This will lead to the creation of a universal public transportation card that can be used across the US and then the world. Long term goal would be the “go to” service for ground transportation.
1. Standard User (members)
This will be the riding public or the users that will access the app for transportation services.
2. Admin User
These users can make/propose changes to the layout, color scheme, and aesthetics of the app but approval will be required from Super Admin to push these updates out to the brander user base of the application.
3. Super Admin User
A user that has full ability to edit app design and coding and the user can approve changes suggested by Admin user.
- This will integrate to an existing login mechanism, the required screen will allow the admins to login.
2. Social Login
- Allow users to register and login using third-party services such as Facebook, Twitter, and Google.
- We wanted to allow the user to login using their Uber or Lyft account. However, we are open to ideas/ suggestions of other ways for the user to login
- Support for Face ID/Touch ID for login
3. Invitations
- Allow users to invite others to use your app via email
4. Introductions
- Present the app and inform users of core functionality using a series of introductory screens.
5. Search
- The User needs the ability to search for a specific/desired ride services in case they aren’t initially presented but should be available in their area.
- The user can quickly send us a note of a missing or desired ride service if it doesn’t show up in their search.
- Autocomplete should be included
6. Location Based Services
- The app must identify the user's location and the location of all nearby transportation services.
7. Notifications
- Remind users to do certain tasks or update them on any new related services or info.
8. Dashboard
- The app’s central or main screen where users can access functionality
9. Account Settings
- Allow your users to adjust settings or specify preferences, such as communication frequency.
10. Help/FAQs
- Include a section dedicated to FAQ or Help content.
11. Marketplace
- This function will be necessary for the production of the universal transportation card. Users need the ability to purchase bus passes, train tickets, etc and use the MYTE app as their scannable proof of purchase
- The user will also need the functionality to request and pay for rides and from ride share (car, bike, and scooter) and taxi companies. This information will be plugged into and pulled from their existing account.
12. Ratings & Reviews
- Another cool feature we wanted to add was giving users status based on how frequently they use the application. For example: Using the application to take any of the available services displayed:
1 to 5 times/mth = Explorer
6 to 10 times/mth = Strategic Traveler
11 to 15 times/mth = Ground Commander
16+ times/mth = Almighty Status
13. Payments
- Allow users to pay in some way; for example, using credit cards, debit cards, PayPal, or Bitcoin.
14. Product Listing
- This feature is to shows lists of services, with individual detail pages for each one describing/showcasing that service.
15. Activity Feed
- Show your users an activity feed of some kind, as they’re used to seeing on Facebook and Twitter, for example.
16. Admin Tool
- Administrative tool or panel to enable direct management of users, content and the application.
17. Social Media Integration
- The app must integrate with social media providers (Facebook, Instagram, Twitter, Google+, etc).
18. Reporting
- The app must have the ability to report/export data on each user role.
19. Contact Us
- The app must have the ability to allow users to contact an administrator/send feedback to administrators.
20. 3D Touch
- Make use of 3D Touch on supported devices.
- This will add an additional dimension where users can access additional functionality by applying varying levels of pressure to the touchscreen. It should display a menu or showing additional content.
- Completeness and accuracy of the areas of functionality and content.
- How well your wireframes provide a consistent user flow and clear information architecture for the application.
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
All requested contest requirements/screens as clickable HTML files.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
We are looking for an intuitive and easy to use "wireframe concepts" that will let us design and build the final mobile user interfaces on the next stage of this project. Think about what are the best UI/UX practices when creating this wireframe.
Round 1
The following are the minimum required screens for Round 12. Social Login
4. Introductions
5. Search
6. Location Based Services
8. Dashboard
11. Marketplace
12. Ratings & Reviews
14. Product Listing
15. Activity Feed
16. Admin Tool
18. Reporting
Round 2
All required screens and features with the implementation of the provided checkpoint feedback.The objective of this project is to create an application that will integrate all ground transportation services and build the most efficient and seamless way to travel under 50 miles.
Example of ground transportation services is Uber, Lyft, Grab, VIA, Lime, charter buses like Greyhound and Mega Bus, and other local transit options.
This will lead to the creation of a universal public transportation card that can be used across the US and then the world. Long term goal would be the “go to” service for ground transportation.
User Roles
We will add user accounts to the app:1. Standard User (members)
This will be the riding public or the users that will access the app for transportation services.
2. Admin User
These users can make/propose changes to the layout, color scheme, and aesthetics of the app but approval will be required from Super Admin to push these updates out to the brander user base of the application.
3. Super Admin User
A user that has full ability to edit app design and coding and the user can approve changes suggested by Admin user.
General Requirements
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The app must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned in screens requirements below and user roles above.
- You MUST use wireframes note pane in every single page you design to explain what cases/items are addressed in that page and what things you added/changed/removed. Use the note pane to make your idea clear and help the client give you constructive feedback.
- You are open to suggest ideas/concept that you think will best fit the app.
Screens Requirements and Features
1. Enterprise Login- This will integrate to an existing login mechanism, the required screen will allow the admins to login.
2. Social Login
- Allow users to register and login using third-party services such as Facebook, Twitter, and Google.
- We wanted to allow the user to login using their Uber or Lyft account. However, we are open to ideas/ suggestions of other ways for the user to login
- Support for Face ID/Touch ID for login
3. Invitations
- Allow users to invite others to use your app via email
4. Introductions
- Present the app and inform users of core functionality using a series of introductory screens.
5. Search
- The User needs the ability to search for a specific/desired ride services in case they aren’t initially presented but should be available in their area.
- The user can quickly send us a note of a missing or desired ride service if it doesn’t show up in their search.
- Autocomplete should be included
6. Location Based Services
- The app must identify the user's location and the location of all nearby transportation services.
7. Notifications
- Remind users to do certain tasks or update them on any new related services or info.
8. Dashboard
- The app’s central or main screen where users can access functionality
9. Account Settings
- Allow your users to adjust settings or specify preferences, such as communication frequency.
10. Help/FAQs
- Include a section dedicated to FAQ or Help content.
11. Marketplace
- This function will be necessary for the production of the universal transportation card. Users need the ability to purchase bus passes, train tickets, etc and use the MYTE app as their scannable proof of purchase
- The user will also need the functionality to request and pay for rides and from ride share (car, bike, and scooter) and taxi companies. This information will be plugged into and pulled from their existing account.
12. Ratings & Reviews
- Another cool feature we wanted to add was giving users status based on how frequently they use the application. For example: Using the application to take any of the available services displayed:
1 to 5 times/mth = Explorer
6 to 10 times/mth = Strategic Traveler
11 to 15 times/mth = Ground Commander
16+ times/mth = Almighty Status
13. Payments
- Allow users to pay in some way; for example, using credit cards, debit cards, PayPal, or Bitcoin.
14. Product Listing
- This feature is to shows lists of services, with individual detail pages for each one describing/showcasing that service.
15. Activity Feed
- Show your users an activity feed of some kind, as they’re used to seeing on Facebook and Twitter, for example.
16. Admin Tool
- Administrative tool or panel to enable direct management of users, content and the application.
17. Social Media Integration
- The app must integrate with social media providers (Facebook, Instagram, Twitter, Google+, etc).
18. Reporting
- The app must have the ability to report/export data on each user role.
19. Contact Us
- The app must have the ability to allow users to contact an administrator/send feedback to administrators.
20. 3D Touch
- Make use of 3D Touch on supported devices.
- This will add an additional dimension where users can access additional functionality by applying varying levels of pressure to the touchscreen. It should display a menu or showing additional content.
Screen Specifications
Mobile: 750px width by 1334px height as screen size resolution.Target User
Target users will be the riding public that will greatly benefit to locate, compare, and purchase the most efficient and desirable path to their destination.Judging Criteria
- User experience.- Completeness and accuracy of the areas of functionality and content.
- How well your wireframes provide a consistent user flow and clear information architecture for the application.
Submission & Source Files
Preview ImagePlease create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
All requested contest requirements/screens as clickable HTML files.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.