Indexing Standards:

Not Applicable = NA Yes = Y No = N

What Makes a Mobile App…..

Accessible?

1. Is audio and voice available and meaningful?
2. Can you easily zoom in and out? (When applicable)
3. Is the App appropriate for any text size?
4. Does the full list of options for the touch interface work?
5. How big can the buttons and navigation on the computer be?
6. Is voice activation or control available?
7. Is audible, clear and vibrant warnings worth considering?
8. Have you practiced your mobile device and the usability features of the app? What kinds of controls on movements are available? (When applicable)

Social?

1. Can you register as an application user or, if appropriate, tweeter on Facebook?
2. You can login through the app?
3. If the app is not in use, should you stay logged in? If not, how does the experience impact the user?
4. Does the application or website support methods of social authentication?
5. Is it effective to exchange media content comments and notes? (Where applicable)
6. How simple are alerts and communications can be disconnected from the app?
7. Social Channel Link and Disconnection Successful? (Where applicable)
8. May I turn off or alter notifications?

Secure?

1. Can we decompile the app?
2. If used, how safe is the cloud server connection? (When applicable)-
3. Is the software safely installed on your computer using any data or temporary data?
4. Is all client data deleted if the device is uninstalled?
5. Does the code authenticate? How does it work?
6. Is my data still secure following an update?
7. Is the user to log out automatically after a certain period?
8. Can the security configuration from other devices or websites be changed? (When applicable)-
9. What happens if the user gets locked out?

What About…

The Product – What Are The Basics?

1. Can I download the app?
2. Can I download an update?(If Applicable)
3. Can I update the app when there are multiple updates available? What happens if I don’t update?(If Applicable)
4. What happens when the OS is updated?
5. With what systems should it be compatible? For example, OS, platforms and browsers.
6. Can I uninstall the app?
7. Can I re-install the app?
8. Can I downgrade? Should I be able to downgrade? (If Applicable)  

Functional Testing – What Does It Do?

1. Does the app perform the designed tasks?
2. Does the app perform non-designed tasks?
3. Does the app ask me to turn on services? For example, location specific, Wi-Fi, and social media.          
4. Is the user redirected? If so, where? From app to Web or visa versa? What do errors look like?
5. Does the user interface (UI) and design work as intended? Is there room for misunderstanding or error or any Corrections?
6. Is the UI appropriate for the form factor? For example, phone versus tablet, screen size, resolution, and existence of hardware buttons or keyboard.
7. Does it comply with any standards, good practice and guidelines?
8. Is the mobile app consistent with the desktop version, if it exists? (If Applicable)

Data – Testing What It Processes

1. How does time apply to the app? For example, phone time and server time? What about time zones?
2. What does it track and update? For example, reward points, friends, purchases, check-ins, social updates and user activity. (If Applicable)
3. Does it sync and update?
4. What happens when it can’t sync or update because the device is…
5. Offline
6. Connected but with no Internet connectivity (Have Wi-Fi connection to router, but Internet connection is down)
7. Connecting through a paywall and haven’t yet authenticated (Wi-Fi in Starbucks, an airport, or a local pub)
8. Disconnected because Web filtering rejected the request
9. Is there consistency between Web and mobile? (If Applicable)
10. How are things like user details and data saved?
11. What about data input and output? What type of data is accepted? For example, locations, preferences, friends, contacts, languages, files, size, media and audio. (You can Add any data types applicable to example list)

What About…

Platform – What Does It Depend On?

1. Change the device settings around. What do you notice?
2. What permissions does the app need?  
3. What tablet device is being used? What version of hardware or software?
4. Review app store submission requirements.
5. Test content. For example, text size, content adjustment and responsive design.
6. Test the UI and touch-screen gestures. For example, swipe, zoom, pinch, multi-touch, shake and orientation.
7. Test peripherals. For example, keyboards, Mi-fi devices, BT peripherals, iBeacon, and syncing peripherals.
8. Test Camera, if applicable. For example, taking photos, using stored photos and photo data.
9. How does the app run when the device is locked?

Operations – How Is It Used?

Be sure to test the app in a variety of situations, such as:                                               

1. Connectivity (Testing under no, low and partial connectivity)
2. Wi-Fi
3. 3G  / 4G
4. Airplane mode  
5. Through a proxy (If Applicable)

How Is Data Saved?

1. Does the app write to the SD card? (If Applicable)
2. What happens if the SD card is full? What happens if it is removed? (If Applicable)
3. Is data saved online (in the cloud)?
4. If the data is saved online, can it be retrieved after reinstalling the app, or will it be available on the app on a different device with the same user account?
5. If the cloud is used, how does lack of connectivity affect the user experience?

Interruptions

How does Our app handle...

1. Phone calls
2. Text messages  
3. App notifications         
4. Forced updates
5. Voicemail
6. Switching between apps
7. Locking and unlocking the screen
8. Music playing while using the app
9. Data app interruptions (WhatsApp, Viber, Tango)
10. Audio interrupts from multiple sources (iPod, Media player, Other audio apps)

Customer Feedback

What are people saying about it?       

1. App ratings / comments (If Applicable)  
2. Comments, forum posts and articles on the (social) web.    (If Applicable)
3. Complaints and support requests  (If Applicable)