The goal of this challenge is to take the provided UI Design and convert it to a native Android mobile application prototype in Portrait view.

 

There is no backend interaction in this challenge, we will have a follow-up challenge to connect the application with backend.

 

This Prototype challenge is part of the HPE Live Blitz Challenge Series. Make sure to check it out!

Challenge Requirements

In this challenge you will develop a prototype Android app that has all screens provided in the provided design.

Note the following :

- The design screens are very detailed to show the flow between the screens. If there is anything not clear please post questions in forums.

- The 11_Style Guide.png show the common UI controls we use in the app.

Screen Requirements

All screens in the screenshots provided are in scope, refer to to the provided files in forums and let us know if you have any questions.

Follow the screenshot numbers to understand the flow of screens, the app is set of modules, each module contains set of questions/steps, at the end of each module there is a screen that show result/badge with options to navigate to dashboard or next module.

If anything is unclear in the flow, please ask in forums.

Note the following about the screens :

- Assessment Flow

    - User gets to this flow by tapping on “Get Started” from landing page.

- Login Screen - We have three flows based on the logged in user (you can simulate this)

    - New User, we take user to 01-2_Login_First Time.png, then we take user to 01-3_Login_Score Low.png or 01-4_Login_Score High.png based on score (Both screens are the same, only content is different, so you can pick any of them but allowing future development to specify the content dynamically)

    - Existing user with low score, we take user to 01-3_Login_Score Low.png

    - Existing user will be taken to dashboard screen

    - Forgot password is out of scope, it is dead link.

- Dashboard

    - Active badge stroke filled area should be dynamically set, it is not static images.

    - Tapping on the widget header will take user to the corresponding module flow.

    - Top icons are dead links, add alert that say “This feature will be implemented in future”

- Profile Screen

    - Only Business tab in scope.

    - Other tabs and notification icon when tapping on them alert “This feature will be implemented in future”

- Module Flow

    - We have multiple modules with same flow, each widget in the dashboard screen represents a module.

    - The module in scope is Business Continuity Planning screens/flow, others are out of scope (to be implemented in follow up challenge).

    - For each step we have “next” button, by default it should say “Skip” until user fill/answer all questions in the step, if all questions are filled/answers then the “skip” should switch to “next”.

- Assessment Levels Flow

    - The screens between 08-0_Assessment lv1_Intro.png - 10-2_Assessment lv2_Result.png represents the assessment levels.

    - Most of the assessment screens in this flow are same as the assessment landing page flow.

    - In the prototype makes user gets to this flow when user finish the BC module.

General Notes

Note the following :

- The app will be in Portrait view only.

- The target screens should target normal and large screens, it should be responsive and proper densities/resolutions should be used as provided in the storyboard.

- The implementation must be a native application, native controls must be used wherever possible.

- The back button should go back in history (i.e. as if you were pressing back in the browser). If there is no more history (i.e. you're at the first page), pressing back closes the app.

Project Structure

You will use Android Studio project for this application. Follow Android Studio project structure best practices.

Technology Overview

- The target platform is Android.

- You will support Android version 4.1.x - 6.x.

- You are allowed to use any supporting open source libraries. Please clearly document use of all such libraries.

- Use of PhoneGap is NOT allowed. We are building native application.

Documents

Provided in challenge forums : the Storyboard and Screenshots

 

Final Submission Guidelines

Deliverable

- Android Studio Project with all source code that addresses the requirements.

- Deployment guide with verification steps.