posted by: Paul DeBeasi
Introduction
Enterprises use many different approaches to develop applications on mobile devices. This post continues a three part series on maximizing return on investment (ROI) for mobile application development. Part 1 explained why mobile application development is so difficult and introduced three common deployment approaches. This post discusses the benefits and challenges of each approach. Finally, Part 3 will provide specific tips to help enterprises maximize mobile application ROI
Thin client
The thin client approach uses a mobile browser to access a server resident enterprise application. This approach has the following benefits and challenges.
Benefits
- Application reuse – Many enterprises can re-use their server-based applications by simply providing mobile browser access to those applications.
- Rapid development time – A thin client application requires less development time that the other approaches because the programmer does not need to integrate with different hardware, operating systems, and software development kits.
- Portable – Enterprises can develop thin client applications that are portable across different mobile devices and browsers. One major caveat is that mobile browser compatibility varies from browser to browser (just like on a laptop). The mobile web initiative can help enterprises develop technical best practices to improve user experience on mobile devices.
Challenges
- User unfriendly – Mobile browsers are notoriously difficult to use. Try browsing the web using this opera mini simulator.
- Requires network connectivity – A thin client requires a continuously active network connection to access the application.
Thick client
The thick client approach deploys a full-featured smartphone-resident application. This approach has the following benefits and challenges.
Benefits
- Native look and feel – Programmers develop thick client applications using software development kits (SDKs) that are native to the mobile device. Therefore, the application can take advantage of the these native application programming interfaces (APIs) to achieve a device-appropriate look and feel.
- Hardware access – The developer has access to the mobile device hardware (e.g., GPS, accelerometer) via the native device APIs (e.g., Apple iPhone SDK).
- Integrated security/management – Some platforms (e.g., Windows Mobile and Blackberry) have very strong built-in security and management capabilities.
Challenges
- Limited portability – A thick client is programmed for a specific hardware/software platform (e.g., Nokia E60 and Symbian) and is therefore not easily ported to a different platform. Writing to an application platform (e.g., Java Micro Edition, .NET Framework, Binary Runtime Environment for Wireless) can improve portability but still lacks the portability of the thin client approach.
- Bigger development investment – Any enterprise that wants to support several different types of mobile phones (e.g., BlackBerry, Nokia, and Apple) and uses the thick client approach, must plan for a bigger development and support investment because each platform requires a unique development effort (See www.deviceanywhere.com for testing resources).
Mobile middleware
The mobile middleware approach uses an abstraction layer that sits between the native mobile phone hardware/software and the enterprise application. This approach has the following benefits and challenges.
Benefits
- Portable – Most mobile middleware systems support a broad range of hardware and software platforms. One of the greatest benefits of using a mobile middleware system is the ability to port applications to many environments.
- Integrated security/management – Some platforms (e.g., Sybase iAnywhere Afaria) have very strong built-in security and management capabilities.
- Integrated applications – Some platforms provide built in mobile messaging applications (e.g., email, instant messaging).
Challenges
- Lack of standardization – Mobile middleware APIs are not standardized. Therefore, an enterprise cannot easily change mobile middleware vendors.
- Cost – Unlike many thick client development platforms, mobile middleware solutions are not free. The enterprise must pay for license fees.
Next time
This post reviewed the benefits and challenges for each approach. In part 3, we look at specific tips to maximize the return on your investment.
Comments