Tablet Applications Apps Testing

Tablet Applications Apps Testing

Tablet App Quality Checklist

Before we produce any apps on Google Play, it is mandatory to confirm that the apps meets all the basic expectation of the tablets user through features compelling and an self-generated, well -designed UI. 
 

Tablet is a growing parts of the installed Android base that provides new offers for the users engagement and monetisation. If our apps are targeting users of tablets, then such document really help us to focus on key aspects of quality, feature set, and UI that can have a significant impact on the app's success. Each focus area is provided as checklist items, with every one comprising multiple smaller best practices and tasks.

Although the following checklist task are numbered for comfort, we can handle those in any addresses or order them to the stage that we aware about right for our apps. In the power of providing the best possible item to our customers, follow the checklist recommendations to the greatest extent possible. 
 

As we move via the checklist, you shall search link to resources support that can help us addresses the topic generated in each and every task.

1. Test for basic tablet app quality
   The starting steps are providing the great experience of tablets apps is confirming that it maps with the quality of core apps, The criteria for all of the device and form factor that the apps are targeting. For full fledged information, Now Just see the Guidelines for Core App Quality.

Before publishing, also make sure that our apps passes multiple basic technical tests and criteria of launch, Like as given below:

• Targets appropriate versions of Android
• Describe properly any hardware dependencies
• Announces the support for proper screens
• Used all of the available space of screen.
• Screen-shots are uploaded on Google Play

If our apps are already uploaded on the Google Play Developer Console, we can check how it is doing against such tests by just visiting the Optimization Tip pages.

2. Optimize the layouts for bigger screens
   Android creates it soft to develop any apps that can execute well on a wide range of devices sizes of screen and form factor. This large characteristic work in our favors, since it help us to design a single apps app that we can Deliver widely to all of our targeted device. However, to provide our user the best possible experience on the configuration of each screen — in individual on tablet — we require to optimize our layout and another UI component for each targeted screens configurations. On tablet, optimizing our UI let us take full advantages of the extra available screens, such as to offers new feature, available new content, or enhance the experience in other way to deepen users conflict.

If We developed our apps for handset and now like to deliver it to tablet, we can begin by developing minor adjustment to our fonts, layouts, and spacing. In few cases — such as for 7inches tablet or for a games with large canvases — these adjustment can be all we require to create our apps look best. In another cases, such as for bigger tablets, we can re-design part of our UI to renew "stretched UI" with an economic multipane UI, additional content and easier navigation.

3. Take benefits of additional area of screen present on tablet
   Tablet screen give significantly more screens for real estate to our apps, especially when it is in orientation of landscape. In specific, 10 - inch tablet offers a greatly area of expanded, but even in 7 inch tablet provide you much more spaces for displaying the engaging users and landscape.

As we consider the UI of our apps when executing on tablet, confirm that it is taking about full advantages of extra screens area present on tablet. Some suggestions given below:

• Look for offers to contains the extra contents or use an optional treatment of existing available content.
• Use multi - pane layout on tablets screen to trust single view into a compounds view. This let us use the extra area of screens more efficiently and create it easier for user to navigate our apps.
• Create Plan how we like to panels for our compound view to organise when screen orientation change.

3. Use Icons & another asset that are designed for the screens of tablets
   To confirm our apps look it is best, give icons and another assets of bitmap for each and all density in the range of normally supported by tablet. Specifically, we should designs our icon for the actions bar, notification, and launch according to the guidelines of Iconography and give them in several densities, so those appears at the correct sizes on all screen without blurring or another artifacts scaling. 
    
4. Adjust sizes of font and touch target for screens of tablet
   To confirm our apps are easy to use on tablet, It require some time to adjust the sizes of font and touch target in our tablets UI, for all of the screens configuration we are targeting. We can set the sizes of font via style able attribute or dimension of resources, and we can adjust touch targets via layout and bitmap drawable, as discussed earlier:

Here are some considerations:

• Text shouldn't be very small or large on the screen sizes of tablets and densities. Confirm that labels are sized fittingly for the elements of UI they match to, and confirm that there are no indecent line break in label, title and another element.
• The suggested touch target size for elements of onscreen is 48dp (32dp minimum) — some adjustment can be required in our tablets UI. Read the Grids and Metrics to acquire about strategies of implementation to help most of our user. To meet the accessibility requirement of decided users, it can be correct to use bigger touch target.
• Whenever possible, for small icons, enlarge the touch-able areas to more than 48dp with the help of TouchDelegate or just centering the icon within the button of transparents. 
  
   
  6. Adjust sizes for tablet screens of home screen widgets
• If our apps contains a screen widgets of home, here is some few points to view to confirm the great users experience on the screens of tablets.

• Confirm that the default height of widget and width are set suitably for the screens of tablets , as well as the maximum and minimum re-size width and height.
• The widgets should be re-sizable to 420dp or more, to span 5 or more rows of home screen (if this is a vertical or square widgets) or column (if this is a horizontal or square widgets).
• Confirm that 9 patch image render perfectly.
• Default system margins need to use.
• Implement the targetSdkVersion of apps to 14 or higher than it, if possible. 
   

7. Offer the full feature set app to tablet users

Let our tablets user experiences the best feature of our apps. Given below are some suggestions:

• Design our apps to offers at least the same set of feature on tablet as these do on handset.
• In rare cases, our apps might replace or omit definite features on tablet if they are not supported by the use-case or hardware of mostly tablets. For examples:
  • If the handsets use the features of telephony but telephony is not present on the present tablets, we can replace or omit the related functionality.
  • Several tablets have few GPS sensors, but mostly users would not generally take their tablets while executing. If our phone apps gives functionality to let the records of users a GPS tracks of their executes while taking their cells, the apps would not require to give that functionality on tablet because the use cases are not compelling.
• If we will forget any feature or capability from our tablets UI, confirm that it isn't accessible to user or that it offer “graceful degradation” to the feature of replacement (also see the sections below on hardware feature). 
   

8. Target the versions of Android properly
   To confirm the broadest possible distribution to tablet, Confirm that our apps properly target the Android version that supports the tablet. Initial supports for tablet was added in Android 3.0 (API level 11). Unified UI frameworks support for tablet, phone, and another device was presented in Android 4.0 (API level 14) and is supported in updated version.

We can set the range of app of targeted Android versions in the file of manifest, in the <uses--sdk> component. In mostly cases, we can targeted the Android versions properly by setting the targetSdkVersion of Android attributes to the highest available API level.

Tablet Applications Apps Testing

9. Declare hardware feature dependencies properly
10. Declare support for tablet screens
11. Showcase your tablet UI in Google Play
12. Follow best practices for publishing in Google Play

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS