Service-Oriented Architecture for Mobile Applications

Information Architects (IAs) must consider the small memory size of the mobile phones and their inability to support large bandwidth connectivity rather than squeezing the original website to be rendered on mobile devices. At present software and hardware such as Java Micro Edition (J2ME), Bluetooth, Global Positioning System (GPS), Digital Cameras of more than 5 mega pixels size, and several others are well integrated into cell phones and such phones are economical, hence, they are well liked and well known to all. Such low cost and improved infrastructure aid in making the mobile phones well suited for developing mobile applications; business, communication or entertainment. Further the authors assert the main concerns for the development of mobile applications lies in poor connectivity and insufficient data storage facility of mobile phones as mobile phones have very poor processing capacity. The authors suggest that because of the above listed constraints data exchange, transformation and user interfacing becomes challenging in mobile phones. They enlist the basic requirements for developing mobile applications, which are developing lightweight application software, low cost, flexible and accessible Service-Oriented Architecture (SOA), well integrated and customized system to match services as required by user and smooth flow of data. Furthermore in order to realize these the authors propose a lightweight SOA for such mobile business applications, which involves transferring specific data as per users’ requirement using business process and data access statistics, performing pro-active loading of data from server as per users’ request, providing asynchronous exchange of data with back end system in offline mode to allow smooth functioning of applications and compressing the transference and storing of data using XML (Natchetoi, Kaufman & Shapiro, 2008, p 27).

The authors observe SOA requires standardized data flow and compression in XML formats enabling storage and processing at lower bandwidths. They recommend that lossy method of data compression is significant as the file size is small and do not alter the application functionality after careful consideration. However, as lossy form of compression requires truncation of data not needed by web service user, client, or data truncation not probable to be used by client, then it is not easy to determine what exact data can be truncated. The authors in their IA design advocate truncation of data never to be used by client, as that does not alter the data precision and ensures sameness of original message and smooth functioning of application functionality (Natchetoi, Kaufman & Shapiro, 2008, p 28).

The authors claim that for fast uploading of mosite IA needs to develop a generic solution allowing automatic filtering of the business objects for transference of respective data required by users to decrease chances of customization required for the respective use case (Natchetoi, Kaufman & Shapiro, 2008, p 28). The transference of only required data and truncation of other data could be established because of commonality of knowledge between systems (Natchetoi, Kaufman & Shapiro, 2008, p 29).

The authors maintain that in the lightweight IA or framework the business objects are serialized, compressed and transmitted to the client as Resource Description Framework (RDF) messages on demand. The exchange is asynchronous and can be done in offline mode as well. The authors also claim that for mobile environment asynchronous mode of communication is more congenial, as the server and client are loosely connected, and mobile devices use different network channels based on communication capabilities, as for example when a mobile device is near to a computer then Bluetooth is used for communication but when it is out of the Bluetooth range then General Packet Radio Service (GPRS) or EDGE technology is used for communication (Natchetoi, Kaufman & Shapiro, 2008, p 29).

In the authors opinion for optimum mobile communication in mobile environment IAs need to design a proactive data feeding mechanism based on the prediction of the existing data used and processed by the client to run the mobile applications smoothly. They ascertain that based on demand pattern of the business object probability distribution guidelines can be set automatically and analyzed by Data Connection Manager (CM) and analyzed and changed if the application is augmented (Natchetoi, Kaufman & Shapiro, 2008, p 31).

Business communication in mobile environment must ensure data security similar to those of desktop environment using the internet. In the IA proposed by the authors claim the security system supports data encryption using a combination of asymmetric and symmetric Primary Key Infrastructure (PKI) and have shorter public keys sizes but similar encryption strength. Moreover in the authors’ IA design data encryption feature is implemented as a replaceable module, substituted with another component (Natchetoi, Kaufman & Shapiro, 2008, pp. 30-31).

The authors conclude that the world of technology is speeding towards wireless network and their IA design for mobile environment allows sufficient exchange and security of business data by proactive feeding, compression of data into RDF files and incorporating an asynchronous offline exchange in the event of poor connectivity between user and client and lower processing capacities of mobile devices sans intensive Java coding (Natchetoi, Kaufman & Shapiro, 2008, p 32). The authors suggest following their lean framework of SOA novel mobile business applications can be incorporated for mobile devices.

Reference: -

Natchetoi, Y., Kaufman, V. & Shapiro, A. 2008, ‘Service-Oriented Architecture for Mobile Applications’, International Conference on Software Engineering Proceedings of the 1st international workshop on Software architectures and mobility, Association for Computing Machinery, NY, USA, 10 May 2008, Leipzig, Germany, Viewed 20 March 2009, <http://portal.acm.org/citation.cfm?id=1370896>

Information Architecture (IA) Conundrum

Experts feel numerous doubts surrounds the role of IA, as their activities overlap with many other peoples’ work, skills and situations in the same industry (Patrick, 2007, p 1). From a work practice point of view their role can be considered to ensure the logical arrangement of content to facilitate easy access to the information for the user depending on the digital environment, whether website development or mobile site development or any other usability (software) device development. So, IA helps to manage the site more easily. However, the ambiguity regarding IA’s role can be explained in terms individuals working as IAs have a variety of educational background, and the context like the size, space and device using IA is ever changing (Robertson, et al., 2007, pp 396-397). Also the concept of this profession is nascent, which is yet to develop and reach its potential (Leung, 2008). Albeit, there are a lot commonalities associated with others’ roles vis-à-vis those of an IA, one thing is certain and that is IA has to concentrate on the design of the device and visualize the concept in a plausible manner for others to realize it and ensure its completion. IAs need to plan the mapping, build storyboards or wireframes, construct prototype, coordinate with stakeholders, and liaison with content providers, when working in digital environment. These roles are exercised by Web managers, but a Project manager or producer can also execute these roles (Patrick, 2007, p 5). In such case the IA person gets to be at the apex and he decides. Earlier researches have shown that IAs are involved in researches conducted for developing the product such UI design and communication of information (Robertson, et al., 2007, p 398).

References: -

Kennedy, P. 2007, The many faces of information architecture, Step two Designs Pty Ltd, Sydney, viewed 12 March 2009, <>

Lueng, L. & Waters, M. 2008, ‘Architects of the Physical and Virtual: Parallel Design Principles in Built and Digital Environments’ in L. Leung (ed), Digital Experience Design: Ideas, Industries, Interaction, The University of Chicago Press, Chicago, Illinois, pp. 93-99.

Robertson, T., Hewlett, C., Harvey, S. & Edwards, J. 2003, ‘”A role with no edges”: The work practices of Information Architectures’, Proceedings of HCI International 2003, vol. 1, pp. 396-400.

General Discussion of Mobile Information Architecture

Statistics show that more than 19 million Australians use mobile phones to facilitate their communication. Global communication networks have transformed mobile phones from being basic into smart phones and i-phones cable of offering web based services. Mobile phones use the Global Packet Radio Service or GPRS to establish connectivity. And are Wireless Access Protocol (WAP) enabled devices. At present the connectivity for 2G phones is quite slow, as for example 56/114 kbs, however, more sophisticated phones such as 3G and 4G incorporating advanced IP services plan to bridge this gap. And then more quality content would be browsed through mobile internet.

At present most of the websites do not easily render on mobile devices. Experts feel that it is not sufficient to make the smaller version of the original website to make it readable on mobile devices. Also work needs to be done to ensure each page is specifically reconstructed for this purpose. Accessibility is a major concern and mobile content providers must adhere to accessibility standards as those prescribed by W3C or .mobi guidelines should be followed in all respects so that users are able to access the mobile site irrespective of the mobile phone brand they use.

Another concern worrying the content providers is the need to strip sound and video to minimize the uploading time and save user bandwidth, for which the user is charged. Sound, video and images need to be optimized or razed to hasten the uploading speed. It is thus recommended that images should be either in jpeg or gif formats.
Last but not least Mobile sites need to be simplistic as screen size of mobile devices and PDAs is much smaller compared to those of desktops or laptops. Ergo, the content needs to be adjusted to reflect this like the most important information should be posted right at the top, as connectivity is slow. Also the total page size should be only 20 kilobytes for the site to be viewed correctly by mobile devices. Navigability should be kept very logical so that the user does not need to oscillate back and forth to access key information. He should find his information quickly and easily. Also categories should be kept to a minimum or up to a maximum of 5. Furthermore the user should be able to get his information by clicking lesser buttons. His entire experience should be encouraging and not exasperating.
In terms of Information Architecture the context also has to be kept in mind, while designing mobile websites. It is felt that normally people accessing mosite are younger and they browse the internet not in the luxury of home or office but in cramped trains or equally uncomfortable spot. Moreover they desire very specific information and are not seeking long and detail explanations of their respective queries. They are in a rush but they want very specific resolutions. IAs have to ensure that the mosite they visioning does that favorably without compromising content quality and discounting speed.

Reference: -

Mobile Website Design, AccuraCast SEO Weekly Headlines, viewed 8 March 2009,

<http://www.accuracast.com/seo-weekly/mobile-web.php>

Mobile Website Design, TotalInternet.com.au: Serious about online business, viewed 8 March 2009, <http://www.totalinternet.com.au/website-design/37/Mobile-Website-design/>

Crumlish, C. 2007, Mobile Information Architecture: Designing Experiences for the Mobile Web, IA Summit 2007, viewed 10 March 2009, <http://www.slideshare.net/xian/mobile-information-architecture>