Developing Mobile Apps for the Enterprise Splitware Mobility Platform Vs. Custom Build

Transcription

1 make IT mobile White Paper Developing Mobile Apps for the Enterprise Splitware Mobility Platform Vs. Custom Build By Nasrin Azari President, Mobile Reach Introduction 1 Native vs. HTML5 Mobile Apps 2 Building and Managing Native Mobile Apps 3 Splitware Product and Methodology 4 How Does it Work? 5 Why Should I Use it? 6 How Much Does it Cost? 8 Custom-Build 8 One of the major components of an organization s mobile strategy involves creating, supporting, updating, and deploying native mobile applications. Use cases that require a high-performing user experience, access to device accessories, and/or operation when network connectivity is unreliable will be more effective with a native mobile application. A key detail to keep in mind is that in order for a mobile application to be successful (i.e. achieve the goals that drove you to build it in the first place), it must be widely adopted and used!! As such, end-user requirements should always drive the decision on how to build your mobile application. Below is a summary of the criteria for building a native mobile application (versus a web-based HTML5 mobile app): Task-based: You want a B2E (Business-to-Employee) application that needs to be high-performing and targeted to a particular task (or set of tasks) Highly-secure: You have strict security and/or data protection requirements Offline-capable: Your users will be working in an environment where network connectivity is weak or non-existent Specific UI requirements: Your use cases depend on a robust user experience that cannot be created via a webbased application [email protected] 1

2 Native vs. HTML5 Mobile Apps The capabilities of native mobile applications far exceed what is possible in a web-based (or browser-based) mobile application, because native mobile apps are only restricted by operating system limitations whereas web-based applications must conform to HTML functionality as well. Therefore, native mobile applications can be significantly more secure, flexible, and usable, and can operate independently of network connectivity, making them the ideal choice for use cases with robust and/or specific requirements. In contrast, web-based mobile applications are ideal for customer interaction, information-access, or any other mobile interface that is meant to be widespread, used in an online fashion, and where users are not overly sensitive to functional disruptions, a basic user interface, or sub-optimal performance. The cost of the superior user interface and functionality of the native mobile app is that it is targeted to a specific mobile operating system and is, therefore, device-specific. In contrast, if you write an HTMLbased mobile app, then it will run within the browser on any webenabled smartphone or mobile device so that you can effectively write a single mobile app and have it run across a variety of mobile platforms. Because of the attractiveness and convenience of a multi-platform mobile application, people often make the decision to go with HTML5, even when their requirements really call for a native app. Usually in this situation, the mobile end-users end up getting very frustrated and the implementation fails. The remainder of this paper will focus on understanding what it takes to effectively build and maintain native mobile apps, and how Mobile Reach s Splitware Mobility Platform enhances your organization s ability to alleviate the challenges of that process. 2

3 Building and Managing Native Mobile Apps Most organizations will, sooner or later, discover a need for one or more native mobile apps to serve their mobile workforce. The discovery may be the result of a thorough analysis of mobile use cases, or it could be the result of a failed web-based solution that didn t meet the end user s needs. Regardless of how you came to 2 the decision, it is important to understand what it takes to build and manage your native apps so that you can ensure a successful implementation and long-term benefits. Building and managing native mobile apps is a true software development exercise that includes all the necessary components of a Software Development LifeCycle: Planning Design Development Documentation Test Production Roll Out Ongoing support and maintenance Handling the reporting and management of errors/bugs Fixing issues and re-deploying updated apps Managing deployment and access to new/changing users Re-designing, re-developing and re-deploying a mobile app Creating and deploying new mobile apps Replacing old apps Maintaining appropriate documentation Initially, when planning for the development of a mobile app, it s easy to lose sight of the long-term requirements in favor of getting a solution out as quickly as possible to meet immediate needs. A common mistake is to focus only on the initial build and release of a pretty cool app only to get stuck when something breaks or stops working due to other changes in your environment. When the app cannot be fixed (because the developer or contractor is no longer engaged), the app gets placed on a shelf, stops being used, and there is a process breakdown. So it is important to understand that if your mobile apps are strategic to your business, you need to have a long-term maintenance plan to keep them relevant to your business and usable to your end users. 2 3

4 If your company is not in software development, or if your business does not revolve around writing and maintaining mobile applications ios expertise, Android expertise, Windows Mobile expertise, etc. then it is not practical for you to build an internal team to handle the creation and maintenance of the mobile apps that you need. In fact, many IT service providers are developing enterprise mobility centers of excellence in order to fill this gap for their customers. This is typically a very successful approach which tends to be much more cost-effective, even in the short-term. At Mobile Reach, we live and breathe enterprise mobile solutions! We have architected the Splitware Mobility Platform for both end-user customers and for IT service providers to enable easier and more effective development, maintenance, and management of native mobile apps for your field technicians and other mobile IT professionals. Splitware Product and Methodology The Splitware Mobility Platform is a highly functional and cost-effective alternative to custom-building native mobile applications, particularly for use cases targeted to IT professionals or field service technicians. Splitware caters to the following: B2E (Business to Employee) applications that are focused on process improvement and task-oriented operations Mobile applications for IT and field services professionals that may require offline operations due to working in remote locations or data centers where network connectivity is weak or not available Efficient data capture in the field Usage of barcode scanners, RFID readers, or other data input modules that are incorporated into the mobile device or can be attached to a smartphone or tablet via Bluetooth or USB A diverse environment that requires the use of a variety of mobile devices, such as smartphones, tablets, scanners, etc. Well-controlled user interface requirements to minimize errors and validate data input An environment where encryption and a highly secure mobile solution is required or desired The benefits that you will receive from using the Splitware Mobility Platform include: A configurable user interface that allows a significant amount of control over the user experience, validation, offline capable operations, etc. A non-coding, cross-platform, development tool that allows very rapid development (and maintenance) of native mobile apps on ios, Android, Windows Mobile, and BlackBerry devices 4

5 Scalability that enables the mobilization of a variety of backend enterprise applications across all of the enterprise-grade mobile devices Support for a variety of barcode scanning and RFID options, signature capture, GPS, Geo-location, file attachments, push notifications and the ability to integrate with specialized device attachments A highly secure mobile environment that incorporates DoD-grade encryption protocols and flexible authentication options A mature, well-tested solution that has been operating in large enterprise environments for 10-plus years Using the Splitware Mobility Platform typically produces desired results in one quarter to one half the amount of time it would take you to custom build the same functionality. For example, a solution that might take you 12 months to custom build would likely take only two months using Splitware. Along with this are the many benefits of a welldesigned, proven software package that has been actively maintained and updated for more than 10 years. With certainty, Splitware will result in a quicker project and a more reliable end product. How Does it Work? The Splitware Mobility Platform is built to enable access to back-end enterprise applications from mobile devices with a robust native user interface. There are three primary components to the system: 1. Splitware Client: this is the native application that runs on the mobile device of choice (Android, ios, BlackBerry, Windows, or Windows Mobile), supports all Splitware Apps, and provides the optimal user experience for mobile end users. 2. Splitware Gateway: this is the component that provides connectivity between all Splitware Clients and the target enterprise applications. For each enterprise application, a Splitware Gateway Plug-in translates data that flows between that particular system and the Splitware Clients. 3. Splitware AppStudio: this is a coding-free, drag-and-drop development environment that allows customers and partners to easily create or modify Splitware Apps that run on Splitware Clients. 5

6 The following diagram depicts how the Splitware Mobility Platform would exist in your environment: Splitware Apps are built or modified within the Splitware AppStudio and deployed via the Splitware Gateway to end-users using mobile devices running the Splitware Client. The centralized Splitware Gateway contains a console that allows an administrator to manage the distribution of Splitware Apps and configure certain aspects of the system. Why Should I Use it? The Splitware Mobility Platform was built to alleviate many of the challenges of building and managing your own native mobile solution: System Integration: Splitware was designed to easily integrate into a complex Enterprise environment. The architecture of the Splitware Gateway assures a clean and straightforward method for incorporating support for Enterprise applications. Mobile Reach provides standard Splitware Plug-ins for the following enterprise applications: o BMC Footprints o BMC Remedy o Oracle o ServiceNow o SQL o HP Service Center o HP Asset Center o CA IT Asset Manager And, in addition to the enterprise product-specific plug-ins, there is an OLEDB plug-in that will support just about any database you need to connect to. There is also a Plug-in SDK that supports highly-specific, custom, or legacy environments via a database, web services, or API integration. 6

7 Lengthy Software Development Cycle: As a pre-built, COTS product, the Splitware Mobility Platform gives you 90 percent of what you need immediately out of the box. When you are involved in a Splitware implementation, you are just focused on designing and configuring your own mobile user interfaces, processes, and workflow. Ongoing Maintenance: As a Mobile Reach customer, you will receive product updates and upgrades that are pre-tested, simple to install, and guaranteed not to break existing mobile apps. Desired changes to your mobile apps can be made within the Splitware AppStudio and immediately deployed to your user community. Ongoing Administration: The Splitware Mobility Platform has a small footprint, and is extremely easy to install and manage. The product hides integration complexity within the Splitware Gateway Plug-ins, ensuring an optimal and tight connection with each backend enterprise app. Security: From its inception, Splitware incorporated a flexible security component to allow for various options for encryption and authentication. Cross-Platform Support: Splitware Clients are device-native and yet they all support and run Splitware Apps, which define mobile user interface, mobile workflow, and process control. Mobile Expertise: Mobile Reach has been providing enterprise mobility solutions for 14 years and holds significant experience in the design and development of effective mobile solutions. In addition, our experience provides practical knowledge around a variety of mobile devices, and task-specific mobile solutions for IT asset management, service management, and field services. Scalability and Growth: The Splitware Mobility Platform was designed to scale readily with your environment. The system supports all enterprise-grade mobile platforms (currently, ios, Android, Windows Mobile, and BlackBerry) and allows connectivity to any number of enterprise applications. As your mobility needs grow, your Splitware implementation can be expanded to support additional use cases, devices and applications. Community: Mobile Reach understands the value of information exchange and has recently launched a forum for all users of the Splitware Mobility Platform. Within the Mobile Reach Community, users can share ideas, examples, and information about their implementations that could be helpful to others. This Community is also the master source of information about the product and the first place to go for assistance and support. Using Splitware ensures a high-quality implementation that will meet your enduser s current needs and will support future changes as your organization evolves. Your implementation will meet your security requirements and will have the capability to protect your organization s sensitive data. The initial solution will be developed in less than a quarter of the time it would take to custom-build, and the ongoing administration and maintenance will be minimal. You can take complete ownership of your solution with the comfort of knowing that Mobile Reach can assist whenever needed and you will become part of a large and growing community of Splitware users who share information and experiences to help each other out. 7

8 How Much Does it Cost? When performing a cost analysis, it is important to consider both initial costs andongoing costs in your equation. As a COTS product, Splitware will have the following costs: Software Licensing: (perpetual or subscription licensing is available) o You will pay a license fee for the production system, which includes the Splitware Gateway and Splitware AppStudio o You will pay a license fee for every user that runs a Splitware Client. Note that the pricing of these licenses varies greatly depending on quantity, so a large number of users means a much smaller per-user charge. Also note that once a user is running a Splitware Client, that user can run any number of Splitware Apps that are built using the Splitware AppStudio. Software Maintenance: o You will pay annual maintenance if you purchase perpetual licensing, or your maintenance will be included in your subscription licenses o Your software maintenance will include phone and support, bug fixes, software upgrades (with new features and functionality), and access to an online community that is constantly updated with information, tips, and hints from other users Initial Mobile Application Configuration: o You may want to hire our consultants (or our trained partners) to build out your initial Splitware Apps, especially if you are in a time-crunch or are resource-constrained (although you can choose to do this yourself via the Splitware AppStudio). Hardware: o You will need to purchase appropriate hardware devices to support your chosen use cases Administration: o You will need to appoint an individual to support the Splitware Mobility Platform and become trained on the Splitware AppStudio. The time and effort required for this effort depend on your implementation and environment, but our recommendation is to estimate between 10% and 25% of full-time, based on your number of mobile end users and the amount of activity (number of Splitware Apps) you expect. Custom-Build In contrast, if you choose to custom-build your mobile apps, you will avoid the license/ maintenance charges, but your initial development, timeline, and ongoing costs will be significantly greater. Considering timeliness, the quality of the end product, and the importance of ongoing improvements to your organization, the value of a Splitware implementation increases further. For more information, please visit or contact us at info@ mobilereach.com or to set up an introductory call. 8