Some ideas of mobile interface design

Software developer Johannes Fahrenkrug in his blog Springenwerk about mobile interface design some of the experience, it is worth reference.

Cross-platform interface is a misconception

Cross-platform interface is an illusion never realized, remember Java Swing? It promises a unified interface on any platform running Java, and this promise never cashes, why?

Cross-platform UI sucks. Cross-platform UI means that it's visually and feels bad on any platform.

Because people like the specificity of their own platform, if you want to develop applications for a platform, you must have a deep understanding of each platform's characteristics. Cross-platform interface means that your interface is like an anomaly on any platform, not just the problem of buttons and windows, but also of style and color. There is no "one size, fit all" interface.

Web page is an exception

The game is an exception, but this can be put down first. If there is an interface that can cross the platform, that is the Web interface. This is because people are used to the Web interface is different.

When the user hits the browser, they know that they are entering a different field.

This is as you enter a bookstore, you know you will see different sizes, different typesetting, different colors of books and magazines, this is like a colorful web page, full of different interface design. But if you see a book in a book series with a different layout, or the next issue of the magazine suddenly changes the layout, you will be surprised that this is like suddenly in the native application of the Cross-platform interface.

Therefore, the user's psychological expectations of the difference brings different effects. Clearly, Web pages provide developers with the freedom to cross the platform. They can develop a common interface that runs on all platforms without being criticized. Just need to pay attention to a problem, do not imitate the native application.

If you mimic a native application, the user expects it to be exactly the same as the native application, and web apps often don't meet this expectation, and, worse, imitate a native application on a platform that looks like an anomaly on other platforms.

What should I do?

Build a platform-independent interface and experience (UI and UX) ... Surprise your users with non-native, but add functionality, animation, usability, which is something they don't expect when they use web apps.

What about the mobile interface?

Similarly, users do not like to see the imitation of other platforms, Web applications do not imitate native applications. Or, do not make that kind of shortcut application, in the user's view, the main screen icon is the application, they do not care about specific implementation details. They will expect this to be a native application and they will be disappointed.

Using web technology to mimic native interfaces on mobile devices can only lead to disappointment.

You have full freedom to create an excellent, unique interface. If you mimic the native interface, users will take the technology you spend your time taking for granted, and they will be disappointed when they see that your application is not as fluent as the original.

The original survivor is a webpage?

First ask yourself a question, "What do I want to achieve with this application?" "If you're not clear, don't do it."

People want apps to be useful, beautiful, amazing or entertaining. If it does not meet the above conditions, do not spend your mind to develop it ... If you want to develop an application, develop an application that you also want to use. Otherwise, don't think about the problem.

If you want to put the application in the http://www.aliyun.com/zixun/aggregation/13811.html ">app Store, users will expect it to be the same speed, interface and experience as the native application." Frankly, the easiest way to do this is to do a native application.

Web technology building applications simpler and faster is a myth. It is likely to take a long time and the user experience is still worse. It is simpler to build a simple native application. If you build it with web technology, it could be more complicated (if you try to imitate the native words.) ）

If you have to do that, try Appcelerator Titanium or focus on strobe. Using a professional platform may reduce your trouble.

Of course, the app Store is easier to get in return. If you are not very anxious about the rewards, or insufficient funds, you can consider developing a mobile Web page or Web application. Excellent web apps are also a challenge.

Will some big companies, such as Google and Apple, agree on a unified Web application standard? Unlikely, they have little interest in cross-platform development and are more interested in the platform exclusivity of the application.

Conclusion

If you want the best user experience, develop native apps. But if you don't like the app Store, and your app doesn't get eclipsed by the lack of native interface and functionality, develop an excellent web application, but don't mimic the native interface.

Web page has its own special things. Use these things to surprise your users with the advanced features offered by modern mobile browsers.

Via Springenwerk

Source: http://www.ifanr.com/52779