10 Common Mobile Implementations Mistakes You Should Avoid – Mistake #5
Mobilefever’s 10 common mobile mistakes guide continues and today we reach the middle of our guide with our fifth common mistake, and a really critical one, but as usual, here’s a preview of our previous chapters:
Previously in “10 common mobile mistakes…”:
About the guide: 10 Common Mistakes You Can Avoid When Selecting and Deploying a Mobile Solution
Mistake #5: Settling on a hardcoded / heavily customized solution:
Every software engineer knows that hard-coding something means you pay less now but you will pay more in the future.
Many of the older mobile applications (or the ones that were built in-house) have been designed specifically per client. Today those solutions are being replaced by much more generic and flexible mobile platforms that allow companies to take control on the behavior of the system, tune it when needed, modify the flows and even build new ones – all using configuration tools or well structured development kits.
In today’s dynamic world, organizations must seek mobile applications that come with serious configuration tools allowing the solution to grow and progress with the organization.
Companies that will fail to understand that need may select a customized solution with limited flexibility and will eventually find themselves replacing their mobile software sooner than planned.
Tip#5: When selecting the mobile software, make sure you get a solution that not only includes an end user application, but also includes a set of administrative tools, configuration tools, and maintainable integration modules.
ClickMobile by ClickSoftware includes a massive set of advanced and visual configuration tools, wizards and dev kits.
When an organization wishes to add a new procedure, or make some changes in existing ones – those changes do not involve any change in the product itself. All the configuration is controllable by the configuration tools – from adding new business objects, changing the characteristics of a process or a user interface – all the way to maintaining dependencies between fields, auto-population of fields, context sensitive scripts, validation points and much more.
ClickSoftware’s Visual Forms Editor for ClickMobile turns modifications to the application UI into something which is more similar to editing a word document, or an office powerpoint presentation.
The best part is that deploying those configuration changes is done completely over the air, meaning there is no need to bring the devices to the office or use a LAN connection for those configuration changes.
To summarize tip #5:
When it comes to mobility, changes are part of the game, and lots of changes. when selecting and deploying a mobile application be prepared to address the following question: how hard and how costly it will be to make modifications to the mobile solution after the project phase ha ended. Make sure the solution provides a decent sets of tools to give your organization the ability to make at least some of the changes without involving the project team all over again.