Skip to main content

iOS Design : 5 Tips to design your mobile application

Image
By

5 Tips to design your mobile application

If you want to make your mobile app succeed, you need to get a great user experience (UX). It is useless to have a good idea if you are not capable of showing it to your users.
While I was defining and structuring my last mobile app, I repeated and repeated what I consider the main goal: keep it simple.
Keep it simple via pinterest


1. Keep it simple

A mobile app should be simple and easy to use for someone who has never use it before, this is, user friendly. The most important features should be identified intuitively and quickly accessed. This is the starting point and despite being obvious, my experience shows that it is frequently forgotten. For example try to avoid creating deep navigation hierarchies.
This simplicity goal can be achieved by selecting an appropriate pattern to structure our application. This pattern depends on your specific needs.
Patterns

2. Consider recommended patterns

Consider using the design patterns published in the mobile developer guides. Native applications and the operative system itself follow these patterns, so do a lot of other mobile applications. Users are used to navigating through different applications in a similar way. If your application behaves differently, users may get confused. As Android developer guide says, if it looks the same, it should act the same.

3. Basic functionality

We tend to fill empty spaces and insert as much information and options as possible. We also tend to add a lot of features that are probably not useful to the users. These additional features delay the app publication date and what it is worse, they make our app more complex. When the definition is done in coordination with the clients or non-technical people, they will suggest more features: “Why don’t we add here this…?”, “Where can we include this function…?”, “I saw this other app that does…”, “Let’s develop some augmented reality functionality, it’s so cool…”.
I think that the best approach is to wait until the app is stable enough, and then start improving it by adding new features. This new features will come up as we use the app day by day.

4. Multiple screens

There are devices in a wide variety of screen sizes and form factors. Scale your app from large tablets to smaller phones, portrait or landscape mode, and focus your efforts on the most common screen sizes. Take a look at the Android dashboards.
devices options

5. Minimize the user effort

Help the user to use your application. Keep form data or the parameters configured in the last search, this will minimize the effort needed to use the app.
The most important data to be stored is the login data. Remember your user. But be careful not to hide all the content before the user logs in. It is a good idea to let the users navigate through much of your app without logging in. The login screen can be an obstacle to continue using your app.
Reference Source : Here
Thanks :)
Keep Coding and Designing :)


Comments

Post a Comment

Popular posts from this blog

WPF-MVVM: RelayCommand Implementation

By
In WPF if we are implementing MVVM pattern then we need to play with Command rather than Events. You can use ICommand interface to create each command class. Implementation of ICommand in a class gives you CanExecute(), Execute() methods which take part in the action performed by Command.   Rather than making Command Class for each Command we can implement a generic Relay Command to get Command. Below is a RelayCommand class that we will implement.   ///   <summary>      ///  To register commands in MMVM pattern      ///   </summary>      class   RelayCommands  :  ICommand     {          readonly   Action < object > _execute;          readonly   Predicate < object > _canExecute;  ...
Post a Comment
Read more

.Net List with Changed event

By
Sometimes we need a List which can notify user when an item is added. Here is the way that you can implement a generic ArrayList which notifies user at the time of an element is added.   using  System; using  System.Collections; namespace  ArchiveData.Logging {    // A delegate type for hooking up change notifications.    public   delegate   void   ChangedEventHandler ( object  sender,  EventArgs  e);    public   class   ListWithChangedEvent  :  ArrayList   {      // An event that clients can use to be notified whenever the      // elements of the list change.      public   event   ChangedEventHandler  Changed;      public   object  NewlyAddedItem {...
Post a Comment
Read more

What is DispatcherTimer in wpf?

By
DispatcherTimer When you want to set a timer working with GUI, you always come across threading problem. The problem is that if you want to send some changes to UI that is constantly/continuously changing then that will make your UI unresponsive or in other words it will hang your UI.   To overcome from this situation, WPF gives us DispatcherTimer threading functionality that will take care of such continuously changing processing on UI thread and that will not hang your UI. We can accomplish same scenario in Win Form , through System.Windows.Forms.Timer and in WPF it is System.Windows.Threading.DispatcherTimer .   Difference between DispatcherTimer and Regular timer (System.Timers.Timer) DispatcherTimer is the regular timer. It fires its Tick event on the UI thread, you can do anything you want with the UI. System.Timers.Timer is an asynchronous timer, its Elapsed event runs on a thread pool thread. You have to be very careful in your event handler...
Post a Comment
Read more