The Bermuda Triangle is a place where ships and aircraft are said to have disappeared under mysterious circumstances. But there’s nothing mysterious, really, about what happens to application development projects when they enter the Mobile UX Bermuda Triangle.
Right before your eyes, schedules crumble, functions and features get dropped, frustrations mount, and users defect for competitors in a sea of bad reviews.
We’ve seen it all. Take a look at the nine paths that projects take on their way to the Mobile UX Bermuda Triangle. Benefit from our insights on how to navigate past this dangerous zone.
- Consistent desktop and mobile experience
- Simultaneous release of functionality
- Shared code and content across desktop and mobile
- Reduced development cost
- Different experience on desktop and mobile
- Separate code bases and development teams
- Staggered time to market
Users insist on all-cloud, all the time. They’re migrating to competitors just for this.
Start with a unified UX design system. Add advanced 3rd-party UI controls. You’ll deliver functionality quicker and get web projects done faster.
Users expect device-agnostic apps. They want equality between desktop and mobile features and functions. And they’re impatient. New features have to come out on all devices at once.
Get input from user studies to be sure. A lot of today’s apps have to be device agnostic. But for others, they use mobile only for specific “mobile-based” activities. Go to function parity when you’re sure it’s appropriate.
Even when we get all features on all devices, users ding us. Our apps don’t work well at all resolutions on both mobile and desktop.
Users expect to learn an application once, then use it the same way on all devices. You have to design for all resolutions from the beginning. Technology won’t save your design later in the process.
We simply don’t know how to make our apps responsive to the resolution of the screen they’re on.
Responsive is hard! Don’t try to make everyone do it! Start with a UX design system that includes responsive behavior so it’s easier. Then give developers tools that make responsive part of their process, not an add-on.
Our UX design skills vary across departments and application teams.
Have your best developers define their methodology, including very specific deliverables. Limit tools to a narrow, common set. Use a documented UX design system so you don’t need brilliant design. Show everyone a working model of a production app as a target.
It’s hard for us to spec and design new functionality on web, iOS and Android.
Design based on the business process, not on the nuances of each mobile OS. Using pre-defined responsive/adaptive panels accelerates design and specification.
We use a range of UI technologies across our desktop and mobile applications. We need to build and retain multiple development teams as well as support different development tools.
You can implement a design system across different technologies, but it’s difficult. Off-the-shelf controls reduce burden, skills and testing. Commit to native mobile only when it’s essential.
1: The design system provides responsive, reusable views that can be implemented across technologies.
2: A UI code library helps organizations standardize.
3: Use of 3rd-party controls minimizes testing.
Our organization struggles to deliver releases with feature parity across all devices on a timely basis. Varying technologies is where it starts. Then, no common development approach. Follow that with no UX design system. It’s amazing we get anything done.
The single most important element to evolve to, we’ve seen, is the UX design system. Even with dozens of tools and processes, if you’re all aiming at a single design nomenclature, things speed up.
We’ve got multiple development teams, multiple technologies and multiple applications. The result: our software development life cycle is not controllable and not sustainable.
Every new technology adds complexity across the entire life cycle. To simplify your SDLC (Software Development Life Cycle), cut down on the number of designs, technologies and tools you use. Look for designs, tools and processes that were built to support multi-device development in the first place.