Mobile User Interfaces
In order for any UI to be successful, the vision and the work process (i.e. the concept design and the visual design / direction) must be there, and the technology must facilitate the implementation of such a vision. The UI vision is the undisputed law as a fundamental part of the device storytelling and brand positioning. Everything else is subordinate.
I would like to use this opportunity to work on Rich Mobile user interface to Make a Good Looking List with Powerful Features, customized Grids, Layouts in other words to make it modern by using Tool kits like Resco Mobile Forms.
I have option to Choose platform from Android, Windows phone and iPhone, out of those I choose to work on Windows Phone because it’s because the most popular development environment in developer community.
Windows Mobile platform represents the largest market share, plus the mobile app can be easily uploaded to the device. We will use Visual Studio and C# programming language. I used the third party’s components as well.
The mobile workforce is rapidly growing. This, together with competitive pressure and advances in mobile networks and technologies, is one of the driving forces behind the growing popularity of mobile business-to-business (B2B), employee-to-business (E2B), and business-to-employee (B2E) solutions. Mobile access to back-end systems can substantially reduce operational costs, increase flexibility, and shorten response times.
Mobile User Interface has become the most core point of the Mobile Business in recent times. The corporate fields are competing with their interface rather than the functionality. And whoever balance the interface with the functionality is dominating the mobile devices market.
Proper navigation and control structures can make mobile solutions more comfortable to use. Likewise the user should not have to enter a lot of data. This can be achieved by letting the user select from predefined lists of items with the help of check boxes, radio buttons, or drop-down lists, for example: Intuitive menus can significantly facilitate mobile browsing and decrease the time spent on navigation. Menus can also help to divide the content into separate parts, for example, by arranging information into a tree structure with appropriate captions. Further guidelines for the creation of user interfaces on mobile devices are available like W3C published a set of rules for preparing HTML for mobile devices
Symbian 4 -- which will show up on smartphones in the beginning of 2011, according to the Symbian Developer Web site -- will have a new user interface, according to the Symbian Foundation.
Some of the Improvements include minimizing user prompts, AutoSaving features to reduce save commands, the same look-and-feel for all applications and a new interface layout.
The proposed user interface will have four main views: contacts, music, photos and applications. Users will be able to create shortcuts, placed on the home screen, to access specific content items or collections.
It will also include Context-based menus, which will be accessed using a long press, and also provide faster access to common commands.
It is clear that the success of the iPhone is due to the entire user experience, and not just the user interface. Nevertheless, the UI obviously plays a vital role, and essentially two key components are involved - excellent underlying technology (software and hardware), as well as an extremely focused vision and design process executed with perfection.
In this Project, I will be focusing on the Basic information on Mobile Devices, Interface and its usability. Based on the Data I collect from different Sources I would integrate the applications and using the open source tool kits and make a Custom User Interface Layouts.
ASP.NET framework makes it easy to build mobile Web application
It's a mobile browser file that contains definitions for hundreds of the top individual mobile devices and browsers that hit Microsoft mobile sites. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.
It detects the mobile device hitting your site and makes available 67 capabilities describing the requesting device. These capabilities range from screen size to cookie support to CSS support. It's everything you need to adaptively render content for mobile phones and devices.
This information is exposed to the developer through the Request.
The format of the .browser file is XML and the schema is defined here:
Browser Definition File Schema
The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browser Caps element was used to define browser definitions in configuration files.
I noticed out how nice and easy it is to get a site to validate as XHTML Strict using ASP.NET MVC (Model View Controller). We can get complete control over every bit that goes out on the wire. XHTML was mainly created in order to create a standard that can be used on a variety of different devices without changes. Unlike with HTML, XHTML code must be exactly how it is specified to be. This is due to the fact that browsers in handheld devices etc. don't have the power to show badly formatted pages so XHTML makes sure that the code is correct so that it can be used on any type of browser.
Languages and Tools for this Project
C#, .NET, WML, XHTML, Visual-Studio, Illustrator, Microsoft Express Design, jQuery
The user experience (UX) has been probably the most talked-about topic in the mobile industry, mostly because we all know that the UX suffers and we all have suggestions of how it can be improved, especially in the post-iPhone era. The graphical user interface has been the aspect of the UX which has garnered most attention historically, and countless software vendors have demonstrated solutions to improve the UI, from better text engines to gesture-based widget navigation.
Wireless technology is well suited for bringing e-commerce to automobiles and other forms of transportation. But however it’s still in developing stage.
Many have touted the availability of Flash on Android devices as a competitive advantage over Apple’s mobile devices, which rely on HTML5 and native apps for their video and interactivity.
While in theory Flash video might be a competitive advantage for Android users, in practice it’s difficult to imagine anyone actually trying to watch non-optimized web video on an Android handset, so it is seen very clearly that flash applications are always a bane for present mobile user interface.
Methods and Evaluations
Adaptation can be classified into server-side, client-side, and proxy-based approaches. In client-side adaptation, the formatting of content to the device properties is done on the device itself, usually with the help of Cascading Style Sheets (CSS). In server-based methods, an appropriate version of content is prepared on a server and subsequently sent to the device. Proxy-based approaches use some intermediary in charge of the adaptation process.
Server-side approaches are usually based on XML/XSLT technology. Content is provided in the form of XML documents which are transformed to different markup languages with the help of XSL style sheets on the server and then sent to the end device. Methods for creating user-friendly mobile interfaces can focus on adapting either content itself, the style and the layout, or the structure of pages.
Adaptation of style and layout includes changes in the formatting and presentation of elements; for example, choosing an appropriate font size or color. Avoiding unnecessary breaks or margins and adjusting the spacing are also good ways to improve the readability of mobile pages.
Structural adaptations refer to the flow of pages and the navigation. The flow structure can be adapted by splitting available information into smaller fragments that are displayed on separate pages by pagination. Alternatively, the data may be serialized in some order depending on selected criteria.
Creating an Effective User Interface Create forms that are resolution, DPI, and orientation aware
This objective may include but is not limited to: query a device’s display capability, docking, anchoring, AutoScale, AutoScroll, Form_SizeChanged event, res2.exe, hidpi.exe Create custom controls
This objective may include but is not limited to: creating a class that extends an existing control, creating a new control by extending a control or scrollable control, overriding On Paint and OnPaintBackground, double buffering Write code to control user input
This objective may include but is not limited to: show or hide the InputPanel, SelectNextControl, set the tab order of controls on a form, Input Panel events, OnTextChanged event Bind data to controls and collections
This objective may include but is not limited to: setting data source on controls (Data Member, Value Member, Display Member), LINQ, generics Write thread-safe user interface code
This objective may include but is not limited to: Control.Invoke, Control. BeginInvoke, Control. EndInvoke, System. Threading, System. Threading. Timer, System. Windows. Forms. Timer Implement a message notification window
This objective may include but is not limited to: Microsoft.WindowsCE.Forms.Notification class; customizing notification messages; configuring message timeout Implement a widget on Windows Mobile 6.5
This objective may include but is not limited to: developing, packaging, and deploying a widget
Pros and Cons
Another important notion in the mechanics of the user interface is the distinction between core (embedded) and downloadable apps. By core apps we refer to the set of applications which:
a) Form the vast majority of the user journey and
b) Are pre-loaded or embedded into the handset ROM at the point of manufacture.
Core applications are typically the idle screen, dialer, main menu, settings menu, browser, inbox, calendar, contacts, camera and multimedia player. Downloadable applications are all apps which can be downloaded post-sales, i.e. by the user.
There are fundamental differences between core and downloadable apps, which impact the developer audience, commercial relationships, technical integration, accessibility and overall commercial importance of these applications.
The next table summarizes the fundamental differences between core and downloadable applications.
95% of user journey
5% of user journey
Idle screen, dialer, inbox, calendar, contacts, ..
Rich User Interface will help to increase the user satisfaction which can turn in to high sales.
More graphics will lead to more investments on making and the final product price will go high. There are other possibilities to mislead the user with the actual service. Finally a mobile device is turning out to be a mobile PC with all regular pc features.
I indeed believe the boundary between Core and Download apps is reducing at least in term of integration capability and UX. I-Phone is definitely a good example for this. Although facilitated by supporting only one form factor/kind of device.
Opening all the phone environment phone book, calendar to 3rd parties is indeed not without risk for OEMs both from a security viewpoint.
However, OEMs should be able to allow 3rd party core apps like calendar, contacts, inbox, etc., to be developed as premium content (selected content only) and downloaded via an app store. This will allow a new type of content, what we‘ve called ‘UI personalities’ to be created. A market of this type is already established in Japan by the 3 major operators
Wireless devices continue to change rapidly. While no one is quite sure what the ultimate wireless device(s) will be, there is definitely a need to ensure that devices can function with one another. There is also the need for a truly global wireless communication infrastructure with sufficiently high bandwidth to satisfy the needs of wireless and m-commerce applications along with good user Interface. The establishment of a wireless infrastructure costs a great deal, and there will be many difficulties ahead for the companies paving the way for m-commerce with a good User Interface.