Type of users:

1. iOS & Android app - End User

2. Web Portal - Admin and Sub Admin

Deliverable 1 - Scope : Mobile Application - End User

Module Description Assumptions/ Comments

Base mobile 1. Application Navigation structure setup NA
application setup 2. Setup of application Language Localization file, internet check classes,
network classes, loading indicators etc.
3. Application permissions handling (Push Notifications, Location
Services)
4. Integration with 3rd party SMS, Payment Gateway services
Splash & Tutorial 1. The app will have a splash screen with logo with a car. 1. Static content to be shared
Screen 2. The app will ask the user for Push notification & Location Services for Tutorial screens.
permissions. 2. Tutorial screens to be
3. The app will have 3 - 4 Static Tutorial screens to display app image and Textual content.
functionalities to user.
Login, Login: 1. Mobile number to be
Registration and 1. User will be able to Login using the below options: changed/ reset/ verified
Forget Password a. Facebook using OTP verification.
b. Gmail 2. User will be able to Reset
c. LinkedIn his account using Email id or
d. Email Mobile number.
2. User will be able to select any of the option from UI. 3. Language localization
3. User will be view the following supported Login methods for Google settings/ Country to be
Play Store: checked for Login/ Signup
a. Email methods selection.
b. Facebook 4. 3rd party integration for
4. User will be view the following supported Login methods for Uber Car Login is assumed.
Wash App Store: 5. Guest user interface is
a. Email, assumed. Login/ Signup is
b. Phone number, not mandatory to access the
app.
Signup: 6. JWT based login/
1. Signup using details as: registration authentication is
a. Mobile Number (to be verified using OTP verification) assumed for app user.
b. User name
c. Email id (to be verified using email verification link)
d. password
2. Mobile Number will be verified during Registration process using OTP
and Email ID would be verified using email verification link.
3. Either one of the verification process is mandatory for user
Registration.
4. User will receive notifications and messages for verification.

Forget Password:
1. User can reset the Password using following options:
a. Email id
b. Mobile Number
 2. Email id will be used for password reset using verification link.
3. Mobile number to be used using OTP verification.
Home Menu User will be able to view following sections in Home menu: 1. Home Menu elements to
1. Exterior Carwash be finalized during design
2. Interior and Exterior Carwash placement.
3. Exclusive Carwash
User Types 1. There will be two type of users in the app for features access: NA
a. Regular user
b. On demand user
2. Regular users will be able to view the automatic complete content of
the app while New users enter each of the specification.
3. Both Free or Premium users have to create account to view the app
details/ structure.
Other services to 1. There will be two type of users inside the app for using car wash 1. Textual and Media
be offered services: comments are supported.
a. Regular user 2. Services can be upgraded
b. On demand user at any time after the
2. Regular will be able to select directly from the app. booking.
3. User will be able to view any of the service which are offered inside 3. There is no limit of
the app. services which can be
4. User will be able to view the list of services in the app with choose.
specifications as:
a. Wax
b. Tar removal
c. Bug removal
d. Seat cleaning
6. User will be able to subscribe to any service to receive notifications
regarding the same.
7. User will be able to see the status of service when the work is in the
process.
8. User can create a specific comment before the cleaning starts. Textual
and Media comments are supported and user can make some specific
service demand.
9. User will be able to view the comments with details as:
a. User name
b. Image
c. Comment description
d. Date and time
10. User will be able to see the assigned person name who is doing the job
for him.
Search Services offered by Uber carwash: NA

1. User will be able to search for services which are being offered.
2. User will be able to filter the results of the services using:
a. Price
b. Time for any service
c. User type: User or service provider

Services:

1. User will be able to filter the results of the service using:

a. Category:
 i. Exterior carwash
ii. Interior carwash
iii. Exclusive carwash
b. Language
c. Price
d. Qualified for
2. Sort Results:
a. User will be able to sort the results using:
i. Price
ii. Time consuming
iii. Category
3. User will be able to select multiple categories from the category list.
4. Multiple filters can be applied to the search results.
Service History 1. Both user and service provider users will be able to view the list of 1. Textual and Media
order in the app with details as: comments are supported.
a. Service Name
b. Price paid
c. Service date and time
d. Review feed
e. Duration
f. Actions:
i. Post a comment
ii. Rate the service
iii. Become a regular member
2. Both user and service provider will be able to add a new comment and
view previous comments on any previous service provided.
3. User will be able to view any previous order inside the app that has
been added to history list.
4. User will be able to subscribe to any new offer to receive notifications
regarding offers from the offer list.
5. User will be able to see the status of service as Live when the service
provider is working and status will be updated as ended, after the
service is done.
6. User can make a comment from the previous service.
7. User will be able to view the comments with details as:
a. User name
b. Image
c. Comment description
d. Date and time
8. User will be able to see the count of total comments after a streaming
is ended.
Payment details 1. User will be able to use the payment gateway for following purchases 1. Part payment is assumed.
inside the app:
a. Credit card
b. Cash payment
2. User will be able to purchase a service by using:
a. Visa/ MasterCard,
3. A user will be able to select a card from the list of cards. Details will
be displayed as:
a. Card name
b. Card number
4. A user will also be able to manage the cards directly from the payment
page as:
 a. Edit card details
b. Add a new card
c. Delete an existing card
Services 1. A user will be able to select any of the service with or without NA
selecting all interior and exterior washing.
2. Services list will have details as:
a. Title
b. Interior/exterior
c. Price
d. Saving
e. Total Rating count
3. Service details: A user will be able to select on a service and will be
able to start a auto service. User to view following details of a service:
a. Service name
b. Duration(how often to wash)
c. Actions:
i. User can add or remove any of the service when
he/she has already subscribed for a service
ii. Service to be done as per demand in the
subscription list
iii. Few additional services are will be shown in
recommendations while adding the service.
iv. After course completion user will be able to click
on continue and will be redirected to next service.
4. Service details: A user will be able to view the list of services inside
the exterior/internal with details as:
a. Service name
b. Service title
c. Description
d. Service type:
i. Exterior wash
ii. Interior wash
e. Duration
f. Actions: user will be able to book now or schedule later to
calendar option
g. Calendar needs to be shown inside the app only and it needs
to be sync with google or apple calendar as well for a
reminder
5. Services can be created with :
a. Name of service
b. Service content
c. Discount if applicable
d. Images
6. Particular service will take particular amount of time and needs to be
auto calculated.
7. User can purchase the service using payment details and payment
gateway mentioned in “Payment gateway” section.
Community Calendar: 1. Comments will be Text
1. A user will be able to book a service using calendar. and video based.
2. A user will be able to view the list of upcoming service from the Uber 2. Audio, video, image
carwash or any event which he/she has subscribed to. comments are assumed.
3. A user can set a reminder for any of the upcoming events or service. 3. Comments cannot be
4. A user can enable/ disable notifications for a particular event or edited or deleted.
 service. 4. No actions can be
5. User will view the service details as: performed on comments.
a. Name 5. No comments history or
b. Date and time logs to be maintained.
c. Merchant name
d. Subscription status
e. Session time
6. Multiple sessions can be subscribed for a single day.
Profile 1. User will be able to view/ update profile related details from this NA
section.
2. Following details would be updated in user profile:
a. User Name
b. Full name
c. Email id
d. Mobile number
3. Mobile number or email to be changed with otp verification and email
verification link respectively.
Notifications 1. User to receive notifications in following ways: 1. Deep linking of the
a. Push notification notifications is assumed.
b. In app notification 2. No user segmentation for
c. Notification history the notifications from Admin
2. User will be able to receive notifications with details as: Panel is assumed.
a. Image 3. Only images, HTML link,
b. Title Textual content is
c. description considered for notifications.
d. Date and time 4. No user segmentation for
3. Notification history: notifications is assumed for
a. User will be able to read/ unread the notifications from the any type of user.
app. 5. All users to receive the
b. User will be redirected to the particular section inside the app notifications related to
from notification history. subscribed streamers.
4. Push & in app notification:
a. User will be able to view the details as:
i. Image
ii. Title
iii. description
iv. Date and time
b. Notifications related to service to be sent to subscribed users
only.
5. Notification events will be used for:
a. App related
b. Update related
c. Promotions/ offers related
d. Orders related
e. Payments related
Settings 1. Notifications On/Off 1. Upto 5 debit/ credit cards
2. Change Password with details can be saved.
3. Manage Cards: 2. No real time chat with
a. User will be able to view/ edit cards details as: Admin and app user is
i. Card Number assumed.
ii. Card Name 3. Feedback notifications to
iii. Expiry Date be sent on email and mobile
 b. Actions: User will be able to add new card or delete any card number.
from the cards list.
4. Change Language: User will be able to change the language from:
a. English,
b. Spanish,
c. Chinese
5. Change Currency: User will be able to change the currencies:
a. USD
b. EUR
c. RUB
d. CNY
6. Logout: User will be able to logout of the app.
7. Feedback:
a. User can manage the feedback from this section.
b. Feedback to be listed in Admin panel and admin will be able
to manage the feedback directly from there.
c. No real time acknowledgement of feedback from either
sender or receiver.
d. Feedback history will be there in the app for end user with
details as:
i. Reported date
ii. Description
iii. Title (pre- listed)
iv. Image
v. Feedback status
e. User will be able to write a feedback using:
i. Title (pre- listed)
ii. Description
iii. Image upload from Gallery (Optional)
Static content 1. Promotions & Offers: Promotion & Offers will
a. Title, have static information and
b. Image, will be displayed inside app
c. Description only.
2. About Us
3. FAQs
4. Privacy Policy
5. Terms & Conditions
Messaging 1. The inbox message screen to be placed inside the app. 1. Real time chat is assumed.
2. The main message default view displays conversations with one row 2. No read receipts
having details as: functionality is considered.
a. User image 3. User would be able to see
b. user name messages count in the app.
c. Description (certain limit)
d. Read/ unread functionality for the messages is assumed.
(coloring will be there)
3. User will be able to filter the messages as:
a. Read
b. Unread (default)
4. The default view is set to Unread then Read messages.
5. Messages to be sorted in latest to oldest order.
6. Text box at bottom of the message thread to type a message and
submit.
7. Messaging should use the instant message format and when user post a
 message, the Mobile notification badge should appear.
8. User to see a notification when the message is received.
9. Notification count for messages is assumed.
10. User to have 1 to 1 chat module to communicate with other user - no
provision for Group chat.
11. No real time acknowledgement of messages from sender or receiver.
12. No chat history to be saved post uninstalling the app.
13. Chat to display details as:
a. Person Name (non-clickable)
b. Person Image (non-clickable)
c. Scroll view to view chat messages (while initiating the chat,
it will be empty)
d. Input chat text field
e. Date and time
14. Text & Image messages are supported.
15. Chat text will appear on the screen inside scroll view with following
details:
a. Chat text
b. Chat Date Time (in following formats)
i. Now
ii. 1 min ago
iii. 5 mins ago
iv. 1 hr ago
v. 5 hrs ago
vi. Yesterday 5:30 PM (12 hour format)
vii. Mon 10:04 AM
viii. 27-08-16 5:48 PM
c. Chat sender name (i.e the user’s name or the person’s name)
d. User’s sent messages will be on right side and Person’s sent
messages on the left side.
16. User will receive a push notification when someone send a message to
him/her. On clicking of a push notification, the user will be navigated
to that particular chat screen

Scope Assumptions:

1. ABC will be used to call the back office and book a slot for carwash. Service charges to be bear by the client for the
same.
2. 3rd party messaging services to be purchased by the client and charges to be bear by the client.
3. No message receipts, Group messaging is assumed.
4. The user should will see the service within the app only.
5. 3rd party videos streaming of Youtube would be embedded using either iFrame inside the app.
6. Video player, calendar and click to call to use Native device elements.
7. Live streams to be displayed inside the app using 3rd party video streaming services of Youtube.
8. Multiple services from a single merchant is assumed. User cannot purchase services from multiple merchants at once.
9. APIs for service and management will be provided from the client side. No GUI for service and management is
assumed in the Admin Panel which will be created by Sumesh.
10. Additional efforts for to create any additional module other than Payment & User Management will be shared by us, if
required.
11. We are to handle User, Reports and Payments management via Admin Panel and effort is shared for the same.
Technical Assumptions:

1. Portrait mode support only, No support for Landscape mode.

2. Real time notification updates for order or booking or others is to be done using 3rd party app.
3. Import of any past or already existing data of events in our system is not assumed.
4. Push & Location permissions to be asked & supported.
5. No app or media share controller for app & content share inside the app is not assumed.
6. Reports metrics to be shared for user data management (upto 5)
7. Assuming that internet checks are already handled for every design screen and APIs.
8. Assuming APIs error handling is to be handled with proper error codes from client side.
9. Assuming that application will have empty states and for those screens to have dynamic content and the same to be
provided .
10. Assuming that the data will be stored in local database rather than local preferences or user defaults. The preferences
should only be used to store data for only few keys.
11. No existing codebase to be used or considered during development or analysis of the system.
12. Newly developed APIs as well as APIs that are already being used in the website to be provided with API
specifications.
13. Designs to be provided with proper PSDs and APIs with proper error handling requests.
14. We can suggest and research for React library which is to be implemented for UI generation for Rich Text, Forms &
HTML5 Video display inside the app.
15. Client to provide a specific Standard iCal for to implement booking and notification purposes for both iOS and Android
and if not, Native calendar to be used.
16. Realmdb to be used for Local mobile storage in the system.
17. Either Microsoft code push, electrode or any other OTA app updates services to be used considering that the service is
available in China as well.
18. Backend to be hosted in AWS/ Alicloud.
19. CMS to be developed from scratch for mobile app. No integration with any existing CMS for the system.
20. Assuming that user authentication to be maintained with proper header tokens in api calls for app users only.
Generation of access tokens for users and expiry of access token after certain interval will be handled.
21. Assuming that dev, staging and prod environments to be setup with separate base URLs to be used inside the
applications.
22. Access to existing storage server, keys to be provided. API touchpoints with details to be shared.
23. Inbox:
a. User to have 1 to 1 chat module, no provision for Group chat.
b. No real time acknowledgement of messages from sender or receiver.
c. Text messages to be supported only.
d. No chat history to be saved post uninstalling the app.
24. No Digital wallet integration is assumed.
25. All the collective summary data will be received via existing APIs only, calculation of summary data is not assumed to
be done by us.
26. Only one account per login is assumed. Accessing multiple accounts under same login is not assumed.
27. Designs: We are considering that the designs (PSDs) will be completely revamped and efforts are provided in the same
manner. In case, the designs (PSDs) are existing, efforts will be revised. Existing PSDs to have:
a. Navigation and UX flow
b. Screens with empty states as well as errors and alerts screens.
c. Screens with Trigger points where the frontend calls the APIs.
d. Screens with proper Field validations
e. Font Type and size details
f. Complete placement of design elements
g. development.
28. Database and Hosting: We are considering following assumptions related to Database and System hosting:
a. Schema of the database remains same for Mobile application.
b. The hosting for system will be done by us and hosting will be done on same cloud provider (AWS/ AliCloud)
and following configurations will be taken care by us:
 i. DNS management
ii. Virtual Machines configuration
iii. Database Server configuration
iv. List of softwares to be installed on the virtual machines
v. Scaling of application and database servers
vi. Load Balancing
vii. SSL/TLS certificate

Application Consideration:

Existing App Code Takeover No

Existing Backend APIs Integration Yes

Creation of App Widget No

Use of 3D Touch No

Import data from existing system No

Use of Social Logins Yes

Use of Location Services Yes

Use of Push Notifications Yes

Use of Contacts Kit No

Use of any device sensor No

Use of Camera No

Use of cloud storage - iCloud, Dropbox, Google Drive No

Use of Local Database Yes

Use of Calendar Yes

Use of Bluetooth No

Use of Media Library Yes

Use of Microphone Yes

Technology Stack:

Hosting & Backend: ● Hosting: AWS/ AliCloud

● Backend:
○ Real time Database
○ Servers: EC2/ ECS (to be provided by client)
 ○ API Gateway
● Cloud Storage: S3/ OSS (to be provided by client)
● Data format (REST - JSON)

Mobile App ● Framework - React Native

○ iOS
■ Support from version 10.x-11.x
■ Language - Javascript (Native React)
■ Local DB - RealmDB
■ Target Devices - iPhone 5, 5S, 6, 6+, 7, 7+, 8, 8+
■ iPad Support - N/A
■ Orientation - Portrait Only
○ Android
■ Support from version 6.x - 8.x
■ Language - Javascript (Native React)
■ Local DB - RealmDB
■ Target Devices - Nexus 5, Moto G, Samsung S4 & S5, Four other
additional devices to be selected in agreement with client
■ Tablet Support - N/A
■ Orientation - Portrait Only

Admin panel ● Browser Support - Safari, Chrome, Mozilla

● Language - Javascript (ReactJS), HTML, CSS
● Theme - will be picked from a predefined Template

Language Support ● English and Spanish

Crash Detection ● Crashlytics

Code Repository ● Github

Development ● Agile with weekly/bi-weekly demos/code reviews

Practice

Offline Mode ● Yes

App store ● Over the air updated via Microsoft Code Push or Electrode (China supported only)
Distribution

App Usage ● App events details to be shared (upto 10)

Analytics ● Google Analytics or any other 3rd party tool to be used

Push Notification ● FCM/ GCM

Efforts:
Designs & Analysis (Mobile App & Admin Portal):
Existing APIs & Code Takeover (Mobile App & Admin Portal):
Backend & Project setup :
Mobile App Development (Native React):
Admin Panel Development (React JS):
Admin Panel - HTML & Theme Development:
3rd Party Services Integration (Payment Gateways, Login Methods, SMS, Notifications & Crash logs):
Quality Analysis (Unit Testing, UAT Reports & Test cases, UAT/ Dev/ Production):
Project Management:
iOS/ Google Play Stores submission & guidelines: