The Ubi Guide Web Service (short-term) App (long-term) would be a web based and mobile app which will enable Ubi Guides to “check in” in particular locations. End users would be able to view the closest Ubi Guide to their location and either go to them, request the Ubi Guide pay them a visit, or request the Ubi Guide call/email/IM/text the user. Upon requesting the Ubi Guide, a selection of categories will appear for the end user to explain the issue, e.g., mobile, delegation, etc. Issues are able to be tracked by category and status of help (requested, helping, escalated, closed); as well as, a text field to enter the specific question. Based on the category selected, recommended resources are automatically emailed to the end user upon submitting the request. The end user can also cancel the Ubi Guide if they deem the resources answer their questions. A notes field is available for the Ubi Guide to expand on the issue once they meet with the end user. Once the Ubi Guide helps the end user, a rating scale appears (5 stars) to aid toward incentives. Issues are tracked in order to run reports on the data (top issues, # of questions, average help time, rating of the Ubi Guide).

 

This concept is inspired by Uber Driving Service in US and guides are more like a set of enrolled people who have skills and wants to help people in and around an area.

 

Currently, little thought has been made on the concept of an admin for this application, if the contestant has more input it would be appreciated.

 

Requirements

• A web-app that can be accessed both on browser and on mobile.

• User can have access in 3 ways

  • Guide - The helper who would log/ check in his current location and availability

    • He would also have an option to check if there is any request in his queue

    • And check-in to a particular location in 2 ways

      • Either enter his location manually

      • Or Check-In on Map (we’ll use google maps for this)

  • End User - would have 2 options after checking the guide’s location

    • Request the Guide to Visit them (Request button besides each Guide in a list)

    • Call/IM/Text/Email the guide (Options to do any of them)

  • Admin

    • Determine what users within the system can  be guides.

    • Control other as of yet undetermined administrative functions.

• There will be a login page and a register page.

  • User can login with his pre registered credentials, or do a reset/forgot password to get a new temporary password.

  • Type - Guide or Customer

  • User can register with following info

    • First Name
    • Last Name
    • Gender (Select)
    • Role -Guide/Customer (this should be asked first as soon as the user clicks on register and should be pre 
    • populated based on that selection)
    • Skill (multiselect) - only for Guide
    • Phone Number
    • EMail ID
    • Address
      • Building
      • Street
      • City
      • State
      • Country
      • ZIP

 

• After login we can have 3 views

  • Guide View

    • Check-In Page

      • User can either select to use Map and check In

      • User can manually enter address

        • Building

        • Street

        • City

        • State

        • Country (Pre populated from user description)

        • ZIP

    • Request Page

      • list of all the Request that is in his queue.

  • User View

    • Request page

      • Previously made Requests

        • View ⇒ Status - Open | Closed | Cancelled

        • Button ⇒ If Open “Cancel”

        • Button ⇒ if Closed “Provide Review”

      • Make a new request

        • Search for Guides

          • Search Box (Global Search, can take name, area nearby, address)

            • Advanced search with Address

          • Once search result are available in a table view

            • Select the Guide

            • Or Click on the Request Button

          • Selection would open a Guide detail page

            • With his current location

            • And Options to Call, Email etc

  • Admin View

    • Guides Page

      • Help to determine what registered users within the system can be guides.

 

 

 

Final Submission Guidelines

Submission Note:

1. Must be compatible with all the major browsers including IE9+, Safari, Chrome and Opera

2. Must have a responsive design catering mobile, tablet, and web browsers

3. Feel free to add a Logo (temporary)

4. Any javascript used must be explained with proper comments

 

Note: Be pro-communicative through forums for updates and design discussion