eBay -GetHelp Android Phonegap Build and Enhancements to existing App

The objective of this contest is to create the Android app for the current Mobile GetHelp webapp that will be used by 3 types of Users (An Exec, Support Admin, Support Specialist). The GetHelp App is designed to manage the collaboration between these 3 types of Users on IT support requests that need to be fulfilled. Think of a hi-touch support application for Exec users, where it offers instant feedback and communication between these users for speedy resolution of support requests and upto the minute status on the requests, thereby eliminating any delays or disruptions into the users normal business.

Final Submission Guidelines

Over the past challenges we have built the GetHelp Mobile web App and also an iOS app that will be provided as an Asset for this challenge to create the Android mobile build for this contest. This contest focusses on the Android build only.

!! The Asset App will be made available to you in the forums for registered members. !!

The GetHelp App is designed to cater Executive users who need IT help. They can initiate their requests through this app in either of the 3 ways (Onsite Support, Call me OR SMS). The current Asset already has all of the functionality covered and working as a pure webApp and an iOS version of the App.

The objective of this contest will be to deliver the following key requirements in the iOS and Android app:

• For the iOS app, we need the following update done, which is to move the Host Server settings option to the Application Settings area that is accessed from the Devices Settings page. Also, add an option button to “Reset the values in the local data store”:

• The objective of the Android app is to exactly mimic the current iOS app implementation, with the Server settings in the Application Settings area.

• For the Admin Console on the back end, add the ability to bulk upload Users, Announcements, rewards from a “csv/xls” file.

• Update the Application Icon with the one provided.

• Introduce a Splash screen for the application, such that it appears when its first loaded.

• Update the current Interfaces with the "Beta" labelled artifacts (i.e. logo/icons) [* Updated Artifacts provided in the Forums along with the existing App Asset].

• Move all Application communications with the Server to "https", we are currently using http.

• {Bug} When a New Announcement is added, and if all the existing announcements have been marked read by the Client user (i.e. Exec User), the notification icon does not show the new announcement. We need to be able to show the Notifications icon on the client UI (i.e. iOS/Android/Web) with this new notification that was just added by the IT user in the backend. 

Key areas to validate the Android app to ensure, that all functionality is intact are:

• Whenever a User Updates the Application Host value, we need to reset/clear the local data store values for this App, such that the user is prompted for the Confirmation code again.

• Ability to store the User Confirmation # in the local data store on the client device (HTML5 data store). The User should be prompted to enter activation the first time when the App is installed. Once, activated, this value should be checked from the local store, and only when not available, redirect the user to activation again (i.e. if the app was uninstalled/reinstalled, or all Application data was cleared, etc.).

• We need to have the app lock Orientation to “Portrait”.

• Notifications Here are the scenarios we need to be able handle very well:

  • Both end users are in the App - In-App updates and Notifications should appear as they appear now.

  • Exec Users phone is in standby, App may still be in memory -- If a status update occurred on an open request, we need the ability to auto-wake / notify the device in standby.

  • Exec Users phone is in standby, App may not be in memory -- If a status update occurred on an open request, we need the ability to notify the device in standby.

• Able to use PhoneGaps QR Code scan API, Implement the QR Code Scan functionality to complete the “Onsite Request” flow.

  • As you realize, every request on the backend will have its own distinct QRCode generated. This generated QR Code will be displayed on the Exec Users interface rt after they select the option “Visit Completed”.

• Validate all the Onsite activity / SMS and Call me flow interactions after the above implementation to ensure we have no dead spots (i.e. buttons with no events/actions or redirects that lead nowhere.).

 

 

Submission Guidelines

• This Solution needs to be a Production quality asset.

• Your Submission should include all the Code elements, and a folder that has instructions for Build/deploy/configure.

• An Overview video of the application code blocks (i.e. Code overview) highlighting the discipline of separation of concerns(SoC) applied.

  • Organized Code Walkthrough

  • Demonstrate Test Execution of your Code simulating all the implemented scenarios

• A Demo video that presents all the Request Activity flows (end to end) that were provided in the form of design mockups.

  • Feature the Build/Deploy/Install and Config Steps

  • Feature all the Functionality

• A Documentation that covers all aspects of the solution (System Architecture / Requirements / Build / Deploy / Install / Configure)