Challenge Summary
Welcome to Next Generation Field Service Application Wireframe Challenge. In this challenge, we are looking for wireframe (Axure) solutions based on requirements from our client. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!
At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.
Round 1
Submit your initial wireframes for Checkpoint feedback:
1. Required features
Notes.jpg: Any comments about your design for the Client
Round 2
Your Final wireframes for all the required pages with all checkpoint feedback implemented:
1. Required features
Notes.jpg: Any comments about your design for the Client
Challenge Description:
[topcoder] has a client who would like to develop next generation field service application using wearable technologies like Google glass’s heads up display.
The winner will not necessarily be chosen based on the best graphic design, but on who can give us the best ideas for a more effective layout or wireframe of this page. There are no hard-and-fast content requirements and that is intentional: wowing the client is the goal!
Google Glass Helpful Links:
- We'll be using the Google Glass Mirror API to accomplish our goals, which means we can push "cards" to the Glass device. A primer on this can be found here: http://glass-apps.org/mirror-api
- Google Glass Demo.
- Google Glass User Interface.
- Google Glass Design Principles.
- Google Glass Design Patterns.
- Google Glass Style.
Screen Size:
- Google Glass follows the 16:9 aspect ratio so a screen (card) size of 640px x 360px would work
- You can also see the cards regions section from here.
Design Considerations:
- Design for Glass: Glass is fundamentally different from existing mobile platforms in both design and use. Build your Glassware with this in mind, and design it specifically for Glass. Ensure the user experience is appropriate for Glass by testing on an actual device.
- Don’t get in the way: Glass users expect the technology to be there when they want it and out of the way when they don’t. Do not annoy users with notifications that are too frequent or unexpected. Provide appropriate controls for your users, so they can interact with your Glassware when desired and ignore it when they don’t.
- Keep it timely: Glass is a platform that is most effective when in the moment and up-to-date. Always deliver fresh and relevant content to users. You also have access to a real-time notification system that can inform your Glassware about certain events, such as when users delete or reply to timeline cards. If your Glassware responds to these notifications, do so in a timely and expected manner.
- Avoid the unexpected: Surprising the user with unexpected functionality is bad on any platform, but especially on Glass, because it is so close to a user’s daily experience. Always be honest about the intention of your Glassware and get explicit permission before you do anything on the user’s behalf.
Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The application must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned in challenge details below.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to
make your idea clearer and help the client to give you constructive feedback.
Required Features:
Field Engineers should be able to do a number of things like:
- Track the service location on the map and reach location. Directions will most likely be provided by Google Glass itself and not the app, however if there is anything that we might be able to assist with getting those directions loaded (like loading a Field Engineer’s upcoming service locations in a list).
- Identify the product, by scanning the BAR/QR code and get contextual product info henceforth. We can depend on every product having a BAR/QR code so Glass will not have to identify objects by other means.
- Troubleshooting: Display of standard procedure to fix a problem using voice commands. The Field Engineer is typically on site to provide service to whatever product was identified by the BAR/QR code he/she scanned in. We would like to provide an intuitive way to look at frequently caused problems and how to troubleshoot them. These might be just text or they might be videos.
- Collaborate: Service engineer is able to connect from the remote location using live chat and stream live video of the install. The Mirror API alone cannot accomplish this either, but perhaps we can provide access to start a Hangout or a call to the service center.
Put yourself in the shoes of a Field/Service Engineer. What tools/information would you want displayed in Google Glass? What would you like quick access to? These thoughts should drive this wireframe design.
Target Audience:
- Field Engineers.
Judging Criteria:
Your submission will be judged on the following 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
- Interpretation of the structure into a clear information architecture
Submission & Source Files:
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
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.