13 must-have features for your next mobile app

1. Feedback system

The importance of having some way for users to provide feedback on your app is critical. Whether it is a button or a link to open an email doesn’t matter; the important part is that you give your users a quick way to report bugs, and provide suggestions or criticisms. Users will appreciate knowing that you are open to their feedback and that their input can shape the future of your app.

2. Usability first

A compelling mobile application must feature an interface that focuses on usability. The best way to do this is to follow the general application hierarchy of widely used apps like Facebook, Instagram and Twitter. User experience bonus points are awarded if it is also beautiful and (pleasantly) surprising!

3. Can you customize?

Make sure that there is a clear way to adjust settings for your app: colors, font sizes and, mo st importantly, privacy settings if it happens to be a social app. The more opportunities the user has to tailor the app to her own taste, the less chance that you will get something wrong. And, if you do, it will simply be adjusted by the user.

4. Keep it simple

It gets tempting to throw in a million small, frivolous features into your mobile app because you think they’re “cool” or good-looking, but don’t. Figure out the few basic things users want and build those couple features, and nothing else. I’d rather use an app that let’s me d o what I want in 15 seconds than a convoluted UX that lets me do things I have no interest in actually doing.

5. Remember, it’s a phone

If you are a small business with a brick-and-mortar operation, I always recommend taking a step back and remembering the core function of a mobile device: It’s a phone. Including the ability for your customer to have an over-the-phone connection with you, while they’re interacting with your mobile application, can go a long way to delivering top-notch customer service.

6. Social media login

Start the user experience out right! Use Facebook Connect or another single sign on technology solution to allow your customers to use their social media logins to sign into the mobile app (and keep them signed in). And always give them a way to retrieve their user name/password or remind them which social network they used when setting up the app.

7. Maintain relevancy

The content in it must be something that is impossible to gain from your website. Stop building apps that are just big web browsers, and focus on pushing relevant information and delivering a richer experience that is beyond what your mobile website can do.

8. Ruthlessly eliminate clicks

If you must ask users to register, sign up, or fill out forms, be zealous about eliminating every possible click, or tap, from the design. Ask for less information. Conversion rates fall sharply when extra work is required to sign up. This is a mistake novice designers make over and over. You only have a short window to hook them, and if they have a bad experience, they won’t try again.

9. Don’t change!

When converting a traditionally browser-based system to a mobile app, make sure not to omit or hide any features, however ‘small’ they may seem. Nothing is worse than failing to find, on the mobile app, that one key feature that you always use on the browser version!

10. Include analytics

As a mobile app developer, one key component is to incorporate analytics into your mobile app. A small business must be able to track and identify their users experience and actions. Most users do not enjoy giving up their location, which is understandable. Tracking a users location is different to tracking and analyzing their expe rience. The data gathered will only help encourage better updates.

11. Offline capabilities

It’s frustrating to users when an app is entirely unusable just because they have a weak signal. Consider how you can build in content or interactivity that doesn’t rely on a wireless signal. It’ll make for a positive user experience while your users are on-the-go, online or off.

12. Go with gamification

Gamification allows users to be interactive and have fun while using the app. People will come back to an app again and again if it provides some kind of value, and short-term fun and competition are always winners.

13. Prioritize speed

It’s very important to make sure the app isn’t slow. People used to despise Facebook because of how slow the mobile app is. It is crucial that your app doesn’t make people wait around while it loads.


Android Playstore guidelines

PRODUCT DETAILS

            1. Title - max 30 characters
            2. Short description - max 80 characters
            3. Full description - max 4000 characters


GRAPHIC REQUIREMENTS for Android App
            
            Icons sizes
                        36*36,
                        48*48,
                        72*72, 
                        96*96, 
                        144*144, 
                        192*192, 
                        1024*1024 

            Hi res Icon = 512*512 PNG
            
            Feature Graphic = 1024 w * 500 h PNG

* All icons must be in PNG format

CONTACT DETAILS

            Website         
            Email 
            Phone

PRIVACY POLICY URL



Video Recorder

Video Capture
  1. Video Recorder
  2. Video Capture best tool
  3. Screencastify Addons for Chrome
  4. https://www.screenmailer.com/

Mobile App checklist

No. Module Sub-Module Test Case Description Expected Result
1 Installation
Verify that application can be Installed Successfully. Application should be able to install successfully.
2 Uninstallation
Verify that application can be uninstalled successfully. User should be able to uninstall the application successfully.
3 Network Test Cases
Verify the behavior of application when there is Network problem and user is performing operations for data call. User should get proper error message like “Network error. Please try after some time”
4

Verify that user is able to establish data call when Network is back in action. User should be able to establish data call when Network is back in action.
5 Voice Call Handling Call Accept Verify that user can accept Voice call at the time when application is running and can resume back in application from the same point. User should be able to accept Voice call at the time when application is running and can resume back in application from the same point.
6
Call Rejection Verify that user can reject the Voice call at the time when application is running and can resume back in application from the same point. User should be able to reject the Voice call at the time when application is running and can resume back in application from the same point.
7
Call Establish Verify that user can establish a Voice call in case when application data call is running in background. User should be able to establish a Voice call in case when application data call is running in background.
8 SMS Handling
Verify that user can get SMS alert when application is running. User should be able to get SMS alert when application is running.
9

Verify that user can resume back from the same point after reading the SMS. User should be able to resume back from the same point after reading the SMS.
10 Unmapped keys
Verify that unmapped keys are not working on any screen of application. Unmapped keys should not work on any screen of application.
11 Application Logo
Verify that application logo with Application Name is present in application manager and user can select it. Application logo with Application name should be present in application manager and user can select it.
12 Splash
Verify that when user selects application logo in application manager splash is displayed. When user selects application logo in application manager splash should be displayed.
13

Note that Splash do not remain for fore than 3 seconds. Splash should not remain for fore than 3 seconds.
14 Low Memory
Verify that application displays proper error message when device memory is low and exits gracefully from the situation. Application should display proper error message when device memory is low and exits gracefully from the situation.
15 Clear Key
Verify that clear key should navigate the user to previous screen. Clear key should navigate the user to previous screen.
16 End Key
Verify that End Key should navigate the user to native OEM screen. End Key should navigate the user to native OEM screen.
17 Visual Feedback
Verify that there is visual feedback when response to any action takes more than 3 seconds. There should be visual feedback given when response time for any action is more than 3 second.
18 Continual Keypad Entry
Verify that continual key pad entry do not cause any problem. Continual key pad entry should not cause any problem in application.
19 Exit Application
Verify that user is able to exit from application with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point. User should be able to exit with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
20 Charger Effect
Verify that when application is running then inserting and removing charger do not cause any problem and proper message is displayed when charger is inserted in device. When application is running then inserting and removing charger should not cause any problem and proper message should be displayed when charger is inserted in device.
21 Low Battery
Verify that when application is running and battery is low then proper message is displayed to the user. When application is running and battery is low then proper message is displayed to the user telling user that battery is low.
22 Removal of Battery
Verify that removal of battery at the time of application data call is going on do not cause interruption and data call is completed after battery is inserted back in the device. Removal of battery at the time of application data call is going on should not cause interruption and data call should be completed after battery is inserted back in the device.
23 Battery Consumption
Verify that application does not consume battery excessively. The application should not consume battery excessively.
24 Application Start/ Restart
1. Find the application icon and select it 2. “Press a button” on the device to launch the app. 3.Observe the application launch In the timeline defined Application must not take more than 25s to start.
25 Application Side Effects
Make sure that your application is not causing other applications of device to hamper. Installed application should not cause other applications of device to hamper.
26 External incoming communication – infrared
Application should gracefully handle the condition when incoming communication is made via Infra Red [Send a file using Infrared (if applicable) to the device application presents the user] When the incoming communication enters the device the application must at least respect one of the following: a) Go into pause state, after the user exits the communication, the application presents the user with a continue option or is continued automatically from the point it was suspended at b) Give a visual or audible notification The application must not crash or hung.

Offline App Guidelines

Browser application caching allows a manifest to be created listing pages that should be cached and made available offline.
Normally, when you visit a URL, a server request is made to return the page. Setting up an application cache manifest 
tells the browser how it can use pages already downloaded rather than just immediately displaying an error when 
there is no longer a network connection.

Local Storage is a standard that retains local web app data(even when the browser is shut down) using a key/value system that works similarly to browser cookies. However, it is differentfrom browser cookies in two important ways. First, cookies are resent to the server with every HTTP request, and it would waste a lot of bandwidth to resend all offline data when the server doesn’t need it. Secondly, cookies tend to max out at around 4k of data, while local storage usually gives an application as much as 5 MB of data to work with per domain. 5 MB may not sound like much, but when used carefully, it can go a very long way in terms of offline local storage.

Local Database removes the 5MB limit of local storage and allowsdata to be indexed so that multiple properties can be queried quickly. This is only an HTML5 proposed standard at present; only Internet Explorer and Firefox have implemented it so far. Safari and Chrome use an older, deprecated system called Web SQL. This means if you need this level of functionality, there is a significant amount of extra work and complexity to supportboth standards across all major browsers. Hopefully, that won’t always be the case and major browsers will conform to the finalized HTML5 specifications.

To decide if Local Storage is good enough, consider these constraints for the app: 1. The total size of data you need to keep offline 2. The number of data items (records) you need to keep offline 3. The number of data properties (fields) you need to search within

How to choose App developement

 

Native

HTML5

Hybrid

App Features

     

Graphics

Native APIs

HTML, Canvas, SVG

HTML, Canvas, SVG

Performance

Fast

Slow

Slow

Native look and feel

Native

Emulated

Emulated

Distribution

Appstore

Web

Appstore

Device Access

     

Camera

Yes

No

Yes

Notifications

Yes

No

Yes

Contacts, calendar

Yes

No

Yes

Offline storage

Secure file storage

Shared SQL

Secure file system, shared SQL

Geolocation

Yes

Yes

Yes

Gestures

     

Swipe

Yes

Yes

Yes

Pinch, spread

Yes

No

Yes

Connectivity

Online and offline

Mostly online

Online and offline

Development skills

ObjectiveC, Java

HTML5, CSS, Javascript

HTML5, CSS, Javascript

 

 


basic testing guidelines

For UI Team :- 

All Pages /Screens should be as per approved designs.

All  browsers should be consider as latest versions.
       1)Google chrome
       2)Internet Explorer
       3)Mozilla Firefox
       4)Safari
       5)Opera

For responsive :- consider device default browser

Atleast consider following resolutions while doing 
responsive development.

1) Asus 360*640
2) Iphone 3S 320*480
3) Samsung Tab 800*1280
4) Ipad 768*1024
5) Iphone 6 375*667
6) Iphone 6 plus 414*736
7) Iphone 5 320*568
8) Kindle Fire 600*800
9) Samsung galaxy tab 600*1024
For UI desktop:-
       1)IMac
       2)MacBook pro
       3)Small ,medium and larger screen desktops

Note:- Use less JavaScript and inline CSS, follow w3c school  
       and google page insights guidelines

For Mobile Team:-

        1)Network related alert
        2)GPS related alert
        3)Device back button should be controlled
        4)provide proper minimum and target OS version as 
          per market for apps.
   
For Functional Team:-

        1)Concentrate on performance while implementing 
          functionalities.
        2)Use simple queries so its execution time 
          will  increase.
        3)All basic validations should require on forms, 
         login page ,sign up page etc.
        4)Flow control
        5)cache management
        6)CMS should be as per requirements.



Important Link to calculate screen resolution

Important Link to calculate screen resolution
  1. calculate screen resolution

Target resolutions for responsive designing

Target resolutions for Responsive design
  1. 320 x 480px
  2. 640 x 960px
  3. 480 x 800px
  4. 720 x 1280px
  5. 768 x 1280px
  6. 768 x 1024px
  7. 800 x 1280px
  8. 1200 x 1920px
  9. 2048 × 1536px

Website Testing Checklist

Important Links Python Learner

Hybrid App Pro's and Con's

Hybrid App Pro's and Con's
  1. Hybrid App tutorial

Important add ons for Chrome

Important add ons for Chrome
  1. Check My Links
  2. IP Address and Domain Information
  3. ColorPick Eyedropper
  4. Web Developer
  5. Nimbus Screenshot
  6. Responsive Web Design Tester
  7. Window Resizer
  8. YSlow

Important add ons for Firefox

Important add ons for Firefox
  1. Web Developer Tool
  2. Yslow
  3. Firebug
  4. Pixel Perfect
  5. Font Finder
  6. MeasureIt

Important Reference Links for Responsive Testing