d

Software Requirements
Specification
For

Whatsapp

Prepared by: Ankit Kumar Mishra(11701400)

Section: K17CE , Roll no. : 23

ACKNOWLEDGEMENT

I would like to express my deepest appreciation to all those who provided me the
possibility to complete this Case Study Report. A special gratitude I give to our
subject Teacher, Mr. Sudhanshu Prakash Tiwari, whose contribution in stimulating
suggestions and encouragement, helped me to coordinate my project especially in
writing this report.
Furthermore I would also like to acknowledge with much appreciation to teachers of
software engineering , an A special thanks goes to my Friends, who help me to
assemble the parts and gave suggestion about the task.
I express my thanks to my institution Lovely Professional University for giving me
an opportunity to make this interesting project. I also convey my regards to all other
faculty members of Department of Computer Science and Engineering and friends
for their help and assistance all through this project.

Once again I would like to thank all my supports from the core of my heart.

Name : Ankit Kumar Mishra

Section: K17CE
Roll No.:A23
Table of Contents

1. Introduction
..........................................................................1

1.1 Purpose.................................................................................................................................1

1.2 Document Conventions........................................................................................................1

1.3 Intended Audience and Reading Suggestions ......................................................................1

1.4 Definitions, acronyms, abbreviations...................................................................................1

1.5 Project Scope .......................................................................................................................2

2. Overall
Description .....................................................................................
.........2

2.1 Product Perspective..............................................................................................................3

2.2 Product Features...................................................................................................................3

2.3 User Classes and Characteristics..........................................................................................4

2.4 Operating Environment........................................................................................................4

2.5 Design and Implementation Constraints ..............................................................................5

2.6 Assumptions and Dependencies ..........................................................................................5

 3. Specific
Requirements .................................................................................
..............5

3.1 Functional Requirement .......................................................................................................5

3.2 Requirements of the Application……………………………………………………… …………9

4. External Interface
Requirements .................................................................................
........10

4.1 User Interfaces ...................................................................................................................10

4.2 Hardware Interfaces ...........................................................................................................10

4.3 Software Interfaces.............................................................................................................10

5. Other Nonfunctional
Requirements .................................................................................
....11

5.1 Performance Requirements ................................................................................................11

5.2 Security Requirements .......................................................................................................11

5.3 Software Quality Attributes ...............................................................................................11

6. Application Analysi

7. Feasibility Study
8.Other Requirements
 1. Introduction
1.1 Purpose
This document describes in substantial detail, the software requirements of WhatsApp, an online
instant messaging application. This document will describe the problems WhatsApp intends to
address, the functional requirements and non-functional requirements of the proposed system.

1.2 Document Conventions

DB Data base

DDB Distributed Data base

ER Entity relationship

1.3 Intended Audience and Reading Suggestions

The
document is intended for all the stakeholders customer and the developer
(designers, testers, maintainers).
The reader is assumed to have basic knowledge of Mobile operating system, database, cloud data and
user account. Knowledge and understanding of UML

1.4 Definitions, abbreviations

1.4.1 Definitions

 User Account
A user account is a location on a network server used to store a computer username, password, and
other information. A user account allows or does not allow a user to connect to a network, another
computer, or other share. Any network that has multiple users requires user accounts.

 Mobile Operating System

A mobile operating system, also called a mobile OS, is an operating system that is specifically
designed to run on mobile devices such as mobile phones, smartphones, PDAs, tablet computers and
other handheld devices.
.

 Last Seen, Profile Picture, Status, Receipts

User can put up a profile picture to indicate his appearance. Last seen of a user indicates the last
point in time when the user used the application. Status indicates the written statement about himself
or his state or mood depending in the usage to all his recipients. Receipts indicate the status the
 message sent to any recipient. Single receipt indicates that the message has been sent from the user’
end. Double receipt indicates that the message has been received by the other party. Blue colored
receipt indicates that the recipient has read the message.

 Network Usage
In order to enjoy seamless benefit of WhatsApp, User is supposed to be connected to Internet at any
given point of time. WhatsApp uses considerably lesser network resources than any other chatting
application available in the market. WhatsApp also provides the user with the option to limit
resources to incoming media.

 Recipient
WhatsApp can be used to converse with more than a single user at any given point of time. The
recipient must also use the application on the other end of the conversation. The Contact
information to which the Whatsapp Account is linked is to be saved in the user contacts in order to
start a new conversation with the recipient.

 Group
A Group of users ranging from 1-256 can be added into a group and can be conversed with at the
same time. Any group user can add new members into the group not exceeding 150. Only the Group
Admin has the executive permissions to remove a member of the group. Group admin can also
provide other members of the group with Admin permissions.

 Broadcast Messages
A user can broadcast same message to 1-150 user at the same time with the broadcast option. Users
with his contact information can only receive the message.

 Privacy
Whatsapp provides seamless ways to save the user’s privacy. User can decide which information is
available for other users to view and which information isn’t. Information like Last seem, Profile
Picture, Status can be put out for view to everyone or only to contacts or no one.

 Database
A databse is a collection of information that is organized so that itcan easily be accessed, managed, and
updated. In one view, database can be classified according to types of content

 Distributed database
A distributed database is a database in which storage devices are not all attached to a common
processing unit such as the CPU, and which is controlled by a distributed database management
system together sometimes called a distributed database system. network.
  Entity relationship
An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical
representation of entities and their relationships to each other, typically used in computing in regard
to the organization of data within databases or information systems.

 User case
In software and systems engineering, a use case is a list of actions or event steps, typically
defining the interactions between a role (known in the Unified Modeling Language as an actor)
and a system, to achieve a goal. The actor can be a human or other external system.

 DFD
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects. A DFD is often used as a preliminary step to
create an overview of the system, which can later be elaborated.

1.5 Project Scope

WhatsApp is a proprietary, cross-platform, encrypted instant messaging client for smartphones. It
uses the Internet to send text messages, documents, images, video, user location and audio messages
to other users using standard cellular mobile numbers .As of February 2016, WhatsApp had a user
base of one billion, making it the most popular messaging application. WhatsApp Inc., based
in Mountain View, California, United States, was acquired by Facebook Inc. on February 19, 2014,
for approximately US$19.3 billion.

1.6 References
webwhatsapp.com

http://www.uianduxdesign.com/ux-designs/whatsapp-user-interface-and-user-experience-design.html

https://www.whatsapp.com/

https://en.wikipedia.org/wiki/WhatsApp

http://www.slideshare.net/

2. Overall Description

2.1 Product Perspective

WhatsApp does not work independently. It works together with the internal servers and sending and
receiving application on either end devices.
 Communication interface: WhatsApp communicates with the internal servers via a communication
network.

Software interface: The messages sent via the communication network are specific to the target
recipient. At any point, two known users will participate in the application.

Hardware interface: The software will run on any device running on iOS, Android, Symbian,
BlackBerry operating systems.

Customer: The customer user interface should be intuitive, such that 99.9% of all new WhatsApp
users are able to use the Application without any assistance.

Message Processing: Every message send through the application is processed by the internal
servers and sent to the recipient. Message processing is done at very high processing rates so as to
avoid delay in the conversations between the users. A maximum of 27 billion messages are
processed in a single day by WhatsApp internal servers.

User interfaces

User Once the application is installed, it goes through the user’s phone book, and upon consenting,
sends a push invitation to connect and chat on WhatsApp. A user enters his or her phone number,
and can then change the phone name.

User diagram
2.2 Product Features
The whatsapp identifies a user by a mobile number andby verifying that number. It sends intant messages and
data to the other users of whatsapp (e.g., pictures, messages, videoes, documents,audio messages) , user can
communicate to the other user of whatsapp by calling them from whatsapp, can seen their last seen detail,
user can create groups and can broadcast message in group to the other users of group, can upload their
profile picture and can set a status, users can hide their details from other users like their profile picture ,
status, last seen, users can block users and also can spam other users, users can save their chat, they can star
important messages.
Product features diagram

2.3 User Classes and Characteristics

Enhancement Requests 1. Last Seen

Client has requested that user be able to see the date and time when his/her contact was last using the
application
.
2. User Profile : User should be able to set their profile picture and a status limited to 150
characters.

2.4 Operating Environment

The hardware, software and technology used should have following specifications:
• Ability to connect to the wifi or mobile network.
• Ability to exchange data over the network
• Touch screen for convenience or Keypad (in case touchpad not available)
• Processor with speed of 500 MHz
• Continuous power supply
• Ability to use camera, gallery, microphone and other services of mobile
• Ability to take input from user
• Device must have 512MB RAM or above
2.5 Design and Implementation Constraints
• Create whatsapp account by entering and verifying mobile number
•In case of network not available
• If not able to exchange data over network, prompt error message "Connection not available"

•In case of not able to access services of mobile hardware

• If eg.camera is not working, prompt error message, "Can’t access camera".

• Lock Account
• If user failed to follow policies of whatsapp
• In case of spamming by 10 users
• Maintain Consecutive marked spam Counter
• Increment spam Counter
• For every consecutive spam, increment logic counter by 1.
• Deactivate the account as the spam number reaches 10

2.6 User Documentation

For user manuals and help use help option in the main menu or visit www.whatsappweb.com and click on
contact us option.

2.7 Assumptions and Dependencies

• Network and data availivility
• Power supply
• Better connection for exchanging data over network/+h7\\g
• L;kb
• Availibility of mobile services

3. Specific Requirements

3.1 Functional Requirements

The functional requirements are organized in two sections First requirements of the application on
any device and second requirements of the network resource to connect to the internal servers of
WhatsApp.

3.1.1 Requirements of WhatsApp

The requirements for the working of WhatsApp Application are organized in the following way
General requirements, requirements for authorization, and requirements for a transaction.
 General Requirements Functional

requirement 1:

 Description: If the application on any device is not connected to the Internet, the
system should display initial display.

Functional requirement 2:

 Description: Send a message function sends a text message to another user of

app.

Inputs: Inputs are characters, including numbers and the receiver contact from contact list.

Processing: Reads the message from the buffer, stores it in the sender`s device DB, pass it to
the Central DB and passes the message to receiver and stores it in the receiver`s device DB.
Sender then gets indication of receiving the message by the receiver and indication of reading
the message by the receiver. (Sender gets mark on the message when receiver gets the
message and double mark when receiver opens the message)

Outputs: Mark at the sender`s side – when receiver gets the message in his device.
Double mark at the sender`s side – when receiver opens the message. The
message itself – stored in Central DB, Stored in the sender`s and the receiver`s devises DB for
history. Notification at sender`s side if the message wasn`t transferred to receiver.

Functional requirement 3:

 Description: User Registration User is able to register for the application through
a valid phone number. On installing the application, user must be prompted to
register their phone number. If user skips this step, application will close. The
user’s phone number will be the unique identifier of his/her account on
WhatsApp.

Functional requirement 4:

 Description: Adding New Contacts The application is able detect all contacts from
the user’s phone book. If any of the contacts have user accounts with WhatsApp,
those contacts must automatically be added to the user’s contact list on WhatsApp.
If any of the contacts have not yet registered on WhatsApp, user is provided with
an invite option that sends those contacts a regular text message asking them to
join WhatsApp along with a link to the WhatsApp application on Google Playstore
or respective store depending on the Operating system the device is running.

Functional requirement 5:
  Description: Send Message User is able to send instant message to any contact on
his/her WhatsApp contact list. User will be notified when message is successfully
delivered to the recipient by displaying a tick sign next to the message sent.

Functional requirement 6:

 Description: Send Attachments User is able to send audio, video and images as
attachments.

▪ Audio formats that the application should support: mp3, wav.

▪ Video formats that the application should support: avi, mp4, flv, gif.

▪ Image formats that the application should support: jpeg, png.

Limitations: File size must not exceed 2MB per message.

Functional requirement 7:

 Description: Broadcast Message User is able to create groups of contacts. User is

able to broadcast messages to these groups.

Limitations: The recipient should have the sender in his contacts to receive the broadcast.

Functional requirement 8:

 Description: Message Status User is be able to get information on whether the

message sent has been read by the intended recipient. If recipient reads the
message, 2 ticks will appear next to the message read.

Functional requirement 9:

 Description: Auto Backup User is able to have all his messages backed up on
Cloud or Internal Storage without ever being prompted. User has the choice of
setting the frequency by which the backup can be made.

Functional requirement 10:

 Description: The Application should be able to connect to Internet automatically

even though the application isn’t opened by the user. The Application should stay
connect to internet at every point of time if the network resources are available on
the device.
Functional requirement 11:
 Description: WhatsApp should be able to distinguish between the network
resources like Wi-Fi and Mobile Data in order to perform media respective
download operation with respect to said so network resource.

Functional requirement 12:

 Description: User is able to set media download preferences with respect to

various network resources available. Media download preferences are with respect
to Wi-Fi and Mobile data and different.

Functional requirement 13:

 Description: Share photo function sends a picture (photo) to another user of

Application.

▪ Inputs: Input is the picture in JPEG, GIF etc. formats and the receiver contact from
contact list.(Name of the receiver in this case)

Sender sends existing photo

Reads photo from the device DB, sends it to receiver, stores it in the receiver`s device
DB, Sender then gets indication of receiving the photo by the receiver and indication
when the photo is viewed by the receiver. (Sender gets mark on the message when
receiver gets the photo and double mark when receiver opens the message with the
photo)

Sender takes new picture and sends it

When sender chooses to send new photo, the camera of sender`s device turns on and
sender can take photo. After that, stores photo in sender`s device DB, sends it to the
receiver and stores it in the receiver`s device. Sender then gets indication of receiving
the photo by the receiver and indication when the photo is viewed by the receiver.
(Sender gets mark on the message when receiver gets the photo and double mark
when receiver opens the message with the photo)

Functional requirement 14:

 Description: Using User’s contact list from the device.

▪ Processing: Imports contacts from user`s device to contacts DB. Then checks
which accounts have the WhatsApp app, by using accounts DB, and then stores this
 information in the contacts DB (synchronization). All contacts that have WhatsApp
Messenger, appear in WhatsApp Messenger contact list on user`s device with status. If
new contact added to contacts list of the device, the synchronization executed and new
contact added (if new contact has messenger).

▪ Outputs: WhatsApp messenger contact list.

3.1.2 Requirements of the Application

Authorization

The internal servers gets a request from a User account to process and send a message to a recipient.

Functional requirement 1:

Description: Internal servers checking if the user is authentic.

Input: Request from the application about it authenticity

Processing: Check if the application is a valid application or not

Output: Valid or invalid application

Functional requirement 2:

Description: If the application is updated or not

Input: Application Version

Processing: Process Application Version

Output: The Application gets the message “Update” if it’s an older and unsupported
application version.

Functional requirement 3:

Description: The Application checks for user data after every update.

Input: Check internal encrypted backup for user data

 Processing: Check User Data

Output: Accepts User data or prompts to register again.

Functional requirement 4:

Description: Changes in encryption codes

Processing: Checks for changes in security encryption code

Output: Prompt regarding encryption changes

4. External Interface Requirements

4.1 User Interfaces

The customer user interface should be intuitive, such that 99.9% of all new Applications are able to
complete their transactions without any assistance

4.2 Hardware Interfaces

The hardware should have following specifications:

Ability to run the Latest Version of Application.

Ability to use Network resources

Touch screen for convenience

Keypad (in case touchpad fails)

Continuous power supply and network supply

Ability to connect to WhatsApp network

Ability to take input from user

Ability to validate user

4.3 Software Interfaces

The software interfaces are specific to a proprietary, cross-platform, encrypted instant

messaging client

5. Other Nonfunctional Requirements

5.1 Performance Requirements

It must be able to perform in adverse conditions extremely slow internet connections and low
battery on device.

Uninterrupted connections

High data transfer rate

5.2 Security Requirements

WhatsApp provides encryption so as to prevent unauthorized access to a message midway. It use
256-Bit SSL encryption to secure data between two users.

5.3 Software Quality Attributes

5.3.1 Availability: The WhatsApp internal Server has to be available 24 hours a day.

5.3.2 Security: The Application should provide maximal security in order to make that much more
transparent there are the following requirements:
It must be impossible to plug into the internal server network.

5.3.3 Maintainability: Only maintainers are allowed to connect into internal servers
6. Application Analysis
Now a days the applications are available for messaging but there is not a single application which
can handle multiple things like messaging, privacy, location sharing, broadcasting, group messages,
file sharing etc...

6.1 User Side

No Hidden Cost

Multimedia :- (Send Video, Images, and Voice notes to your friends and contacts)

Group Chat

No need to Log In/Out

No need to add Buddies

Record voice messages.

Know when people have seen your messages.

Status Update

As Open As SMS

And Much More (Share location, Exchange contacts, Custom wallpaper, Email chat history,
Broadcast messages)

6.2 Developer Side

Hardware Requirements (Recommended):

60 GB HD
Android Phone (optional)
I-3 or above processor
2 GB RAM

Software Requirements:
Operating System: Windows XP or above, LINUX
Software: Mobile IDE Plugins
Development Tools: Android SDK
Database: SQLite

Minimum requirement API-13

 7. Feasibility Study

7.1 Technical Feasibility: System will work on android mobile or tablet which requires android 2.1
and up version. Easy to develop application using open source.

7.2 Economic Feasibility: This application is developed using open source software. So, there are
not any issues related to development tools. After develop this application, we will put it on Google
play which is also an open source so user can easily download.

7.3 Operational Feasibility: The system will be GUI based so the user will easily understand and no
need for training. The system will give fast response. It’s a faster way to communicate.

8. Other Requirements
Application must work on all mobile and tablet devices. User interface must be consistent on all devices.

Long Term Plans

Future plans include providing inline document viewer that lets users view pdf and word attachments within
the application chat window itself. Further optimizations can be made to improve performance especially
over the network. This includes making most network specific requests as non-blocking background
processes. We also aim to expand our infrastructure to include more database servers so as to take back up of
user data more frequently.

Maintenance and Support Costs

Maintenance will be handled by in house team of developers in the first 6 months post application launch.
Within this period, we aim to hit our target of 100,000 users. Once this target is achieved, we intend to
outsource maintenance and support to a third party who will be trained for 4 months on system maintenance
and troubleshooting.

8.1 Data Base

The Application must be able to use several data formats according to the data formats that are
provided by the data bases. A transaction should have all the properties of a data base transaction
(Atomicity, Consistency, Isolation, and Durability).

8.2

Appendix A: Glossary
DB Databaase
 DFD Data Flow Diagram

UML Unified Modeling Language

XMPP Extensible Messaging and Presence Protocol

ER Entity Relationship

Appendix B: Analysis Models

_________________________________________

Design Phase
Design phase deals with transforming the requirements, as described in the SRS document, into a

form that is implemented using a programming language. The various designs of this system are

shown as following:

1. Data Flow Diagram:

Data Flow diagram is a graphical representation of flow of data throughout the information system.
Data flow diagrams illustrate how data is processed by a system in terms of inputs and outputs.

Name Notation Role

Process Transforms incoming data

flow to output dataflow
Data Store Repository and their
data system

Data Flow Dataflow are pipelines

through which packet of
information flows
External Entity System entitys are object
outside the system with which
system communicates
  WHATSAPP ARCHITECTURE

 XMPP-Extensible messaging and presence protocol

 SMTP-Simple mail transfer protocol
STATE DIAGRAM
SOFTWARE TESTING

 Manual test cases of : Whatsapp

 Basic testing on whatsapp: Boundary value analysis testing to find whether the
application is accepting the expected range of values and rejecting the values which falls out of
range. The most common example for considering boundary value analysis on whatsaap
testing can be taken as there user trail period example. The free trail period last for only one
year.

1. Verify that on downloading whatsapp application, user can register using a new
mobile number.
2. Verify that for a new mobile number user will get a verification code on his
mobile and filling the same verifies the new user account.
3. Check the maximum number of incorrect attempts allowed while filling the
verification code.
4. Verify that registering an existing mobile number for new user account
registration is not allowed.
5. Verify that on successful registartion all the contacts in user's contact directory
get imported to whatsapp contact list.
6. Verify that user can set DP and status on whatsapp.
7. Verify that user can update existing DP and whatsapp status.
8. Verify that user can send message to any individual selected from his contact list.
9. Verify that 'Chats' window contains all the chat list with DP and name and last
message preview of the other person with whome chat was initiated.
10.Verify that clicking a chat in the chat list opens a new window containing all the
chats received and sent with the other person.
11.Verify that user can check the message delivered and read time for a message in
the 'Message Info' section.
12.Verify that user can share or receive a contact with the other person.
13.Verify that user can create a group adding multiple person from his contact list.
14.Verify that user can send and receive message in group chats.
 15.Verify that user can send and receive images, audio, video, emoticons in chat to
individuals.
16.Verify that user can send and receive images, audio, video, emoticons in group
chats.
17.Verify that user can send and receive chats in secondary languages available.
18.Verify that user can delete text, images, audio, video messages within a chat.
19.Verify that user can clear complete chat history in an individual or group chat.
20.Verify that user can archive chats in an individual or group chat.

Chat settings test scenario

1. Verify that user can set a chat wallpaper.
2. Verify that user set privacy settings like turning on/off last seen, online status,
read receipts etc.
3. Verify that user can update notification settings like - notification sound, on/off,
show preview for both group and individual chats.
4. Verify that user can take the comlpete chat backup of his chats.
5. Verify that user update his phone number that is used by whatsapp application.
6. Verify that user can disable/delete his whatsapp account.
7. Verify that user can check data usage by umages, audio, video and documents in
whatsapp chats.

Change DP and Search Scenario

1.verify the user can upload his profile picture

2.verify the user can delete his current profile picture
3.verify that user can remove his profile pic.;pture
4.verify that user can display a new profile picture.

Scenario of whatsapp group

1. Verify if user can create a group
2. Verify if user can add single/multiple participants to group
3. Verify if user can remove single/multiple participants from group
4. Verify if group admin can make admin to other participants
5. Verify if user can exit from group
 6. Verify if user can delete group
7. Verify if user can send text message/ image /document/ contact/ location /
emoji to the group
8. Verify if user can send multiple text messages/ images /documents/ contacts/
locations / Emojis at a time to the group
9. Verify if all the participants receive message at the same time
10.Verify if user can view if other users have seen his/her message in 'info' section
11. Verify if participant who is not admin can add other participants to the group
12. To check if all the participants can add/edit group name
13. To check if all the participants can add/edit group picture
14. To check if user can view previous chat history of the group
15. To check all the messages in the group are displayed date and time wise
16. To check single tick when message is been sent to group
17. Verify if user can forward messages to single group
18. Verify if user can forward messages to multiple groups
19. Verify if all the users can view other participants and their profile
pictures/Status in group
20 Verify if user can add any participants' contact to his contact list from group
21. To check if user can create broadcast list
22. To check if user can add contacts to broadcast list
23. To check if user can send message/ Emojis /image /document/ audio/ video etc.
to broadcast list
24. To check if user can delete broadcast list
25. To check if user can delete only group chats

Scenario of file-attachment
1. Verify if user can send image as an attachment
2. Verify if user can send document as an attachment
3. Verify if user can send Contact as an attachment
4. Verify if user can send any location or his live location
5. Verify if user can send audio/videos as an attachment
6. Verify if user can record and send voice message
7. verify if user can open any attachment
8. Verify if user can remove any attachment

Scenario of video call

1. To check if user can make video call
2. Verify if user is able to view other user and himself on call
3. Verify if user can hear voice clearly
4. Verify lagging time when users not in same region
5. Verify if user can keep a call on speakers
6. Verify if user can keep call on hold
7. Verify if user can mute call
8. Verify if user can view call logs history

Performance Testing

 To check the performance and behavior of the application under critical condition
as low battery, bad network coverage, low available memory.
 Affected from both the sides , server side and client’s side.

Load Testing
 Concurrent number of users on this mobile web application.
 A load test.
 Understand the behavior of the system under a specific expected load

Configuration Testing
 Tests are created
 Determine the effect of configuration changes to the whatsApp application
 Eg. Making different load-balancing to the system with application running

Isolation Testing

 Repeating a problem causing test execution

 Isolated and confirm the fault domain

Memory leakage testing

  Memory leakage happens when a computer program or application Is unable to
manage the memory it is allocated resulting a poor performance of the
application and overall slowdown a system.

Interrupt testing
 The whats app application should be able to handle these interrupts
 In coming and outgoing SMS and MMS
 Incoming and outgoing calls
 incoming notifications
 battery removal
 Device power cycle network outage and recovery

Installation testing
 It verifies that the installation process goes smoothly without the user having
to face any difficulty
 This testing process covers installation,update and uninstallation iof the
application

Module testing
 Large programs cannot partially tested at once there is large need of
breakdown the programme into module so it is easy to test the application
module by module it prevents from the error

Compatability testing
 Whats app is software that work most of the platform and devices like nokia s
40,Symbian,windows,blackberry os,apple ios,android