Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build mobile apps for iOS, Android and Windows Phone
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Automate decision processes with a no-code business rules engine
Mobility is a hot buzzword. Put the word mobile in a budget proposal and odds are good it will go straight to the top of the pile. But wait—not so fast!
Organizations are still all over the map in terms of mobile development. Some have completed their first generation approach and are assessing their go-forward plans. Some are just beginning to address the role of mobility in their operations, while others are in the planning stage. Some organizations want to “mobilize” existing application functionality, while other organizations want to build brand new mobile apps.
Business apps are all over the map as well—with some companies creating customer facing apps, some building internal applications, and some doing both.
But do organizations really know where they are going, what they want and whether they will get it with all these investments? Maybe not. Perhaps that’s why I’ve been seeing a refinement of thinking going on. No one I’ve talked to wants to reverse course, exactly, but want their new approach to be a little less rushed and more strategic.
One new approach is called mobile-first but is actually a misnomer. The philosophy behind mobile-first is to ensure that the design experience works for users, and works effectively across the entire spectrum of digital devices.
User-first app development considers a user's environment, work style and other factors.
As I have written before, a better name for this approach is “user-first.” We should design the experience for the user based on his or her environment, the type of application, their work or lifestyle, and other variables. The user-first approach requires focusing on their needs and wants rather than starting with the limitations of a particular device or medium.
Why is this important? Well, we have all experienced sub-optimal application experiences—and not just in the mobile world. As a consumer, If we have a sub-optimal experience, we will likely move to another option. This has a direct impact on bottom line. For employees, too, the impact of a poor application experience can hurt productivity and morale. In either case, there are good reasons to address the challenge.
User experience isn’t an easy situation to address since it is complicated by multiple factors, including:
From a technical perspective, there are other challenges:
The bottom line? By all means, embrace mobile, but make sure the user experience is front and center in your design and architecture approach. That will ensure that the investments you make are as effective as possible, and not just money thrown after a trend.
For more on adopting a user-friendly mobile development approach for your business, download my latest whitepaper, “9 Essentials to Create Amazing Applications Faster.”
We’d love to help you get started with low-code, high productivity development tools that can spark your next great idea. Contact us now and we’ll get back to you right away.
Mark Troester is the Vice President of Solutions Marketing, Digital Transformation at Progress. Mark has extensive experience in bringing application development and data integration products to market. Mark previously led product marketing efforts at Sonatype, SAS and Progress DataDirect. Before moving into marketing, Mark worked as a developer and developer manager for start-ups and enterprises alike.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.