Challenge Overview
Project Overview
The goal of this project is to provide maintenance drivers with a mobile app that allows them to update work orders on their delivery route. The app will also provide near real-time update to routes and work order details through an API. Target users of this app are maintenance drivers employed by partners of Rehrig Pacific.
Competition Task Overview
The purpose of this challenge is to build a prototype Android app based on the provided screen design. Please follow these requirements while building this prototype app:
- The prototype app must be built using Java and Android Studio
- The prototype app must follow the provided screen design
- The prototype app must work on Android phones and tablets (i.e. this is a universal app)
- The app only needs to work in portrait mode
- The prototype app will work with a web service API to get route / work order data and we'll provide one by Friday (EST). Before you get the API please use a static json file that contains such data, there should be no hardcoded data in the app.
- Detailed deployment and verification details must be provided in the deployment guide
Features
Here's a high level list of the features we'll need built into the prototype app:
- Provides user with an inventory of items to be delivered on the next route.
- Shows user the next destination in the route and which items are to be delivered, or picked-up
- Allows the user to click the address of the next route item and link to any mobile map program (google maps, apple maps, etc), similar to how you click an address in a contact and then the map app opens.
- Provides a edit screen for each work order ( destination ) on the route, so the driver can provide details.
- Allows driver to attach notes or a single photo to each work order.
Devices
The prototype must support Samsung Galaxy Tab (7'' and 10'') and mainstream Nexus and Samsumg phones.
Notes
- Inventory must be fully loaded before the user can start the route
- In "Driver 5.png", we'll have the following statuses in the drop down:
- Delivered
- Unable to Deliver
- In "Driver 6.png", we'll require the user to manually enter the serial number. We'll consider barcode scanning an enhancement and pay a bonus prize for it.
- Work order: each driver will receive a series of service tickets or cases, we call these "Work Orders". Each work order contains a single address. Tehse addresses are used as the route. Each work order also contains instructions as to which assets are to be delivered and which assets are to be picked up:
- If an asset is to be picked up, a specific asset tag or serial number is included
- If the asset is to be delivered, or the type of asset is specified, once delivery is complete the user will update the work order with the asset number.
- Show Completed Route Stops acts as a filter. The list of work order stops will always show uncompleted ones. Completed ones can be optionally included or not using this option. Whenever this option is changed, the list should update.
Timeline
This challenge has shorter screening / review / appeals / appeals response / aggregation phases, make sure you pay attention.
Technology Overview
- Java
- Android 4.4.x (Kitkat) and 5.1.x (Lollipo) must be supported
- Android Studio (please use the latest stable version)
- Android phones and tablets
Documentation Provided
Please register to download screen design from challenge forum.
Final Submission Guidelines
Submission Deliverables
A complete list of deliverables can be viewed in the TopCoder Assembly competition Tutorial at: http://apps.topcoder.com/wiki/display/tc/Assembly+Competition+Tutorials
Below is an overview of the deliverables:
- A working prototype app that covers all screens from the design.
- A complete and detailed deployment document explaining how to deploy the application including configuration information.
- Demo video is not required.���
Final Submission
For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.