Your Privacy

This site uses cookies to enhance your browsing experience and deliver personalized content. By continuing to use this site, you consent to our use of cookies.
COOKIE POLICY

Skip to main content

Choosing a Mobile App Platform, Native or Hybrid?

Choosing a Mobile App Platform, Native or Hybrid?
Back to insights

It’s the mobile development debate that has raged since JavaScript wrappers evolved to support hybrid, multi-platform development. As the underlying technology of each option has matured, it’s worth taking another look at which option is right for your application. As always, the unhelpful, short answer is still, “It depends.”

Going Native

The development tools for both Android and iOS have advanced significantly in the last couple years. Android released Android Studio, an official IDE for native Android development which replaced Eclipse as the go to environment. iOS released the SWIFT programming language, largely ousting the cumbersome Objective-C language from the development process.

The maturation of these tools means development time should be less than a few years ago and documentation is much better to help resolve any issues that the developer encounters. It’s also likely that finding qualified developer talent is easier than in the past too, now that the platforms are more accessible.

There is also a user experience benefit to taking the native route if you use the built-in navigation and control elements. Users of both platforms are conditioned to understand native defaults and you have to go out of your way to significantly change or avoid using them. Keeping UX in mind is always valuable, but you get the value of a huge team of experts working for Android or iOS backing up your decisions by choosing the default elements.

The major downside to native development, as it has always been, is if you need to release for multiple platforms, you really have to develop your application twice. This is the major factor that really enables hybrid JavaScript applications to continue to compete in the mobile space.

Take the Hybrid Road

The number of options for creating a hybrid application has multiplied in recent years. With the rise of JavaScript frameworks and the maturation of mobile wrappers, like Cordova, you can make a sleek, native-like application that works on several different platform using one code base…at least hypothetically.

Slogging through the dozens of platform choices to figure out which you should use for your application is a serious chore. The variety of choices is great because you’ll have so much flexibility, but it’s a lot of work to figure out which platform will do what you need without bogging down your app with unnecessary bloat.

The complicating factor is that you have to make several different technology decisions. You need a native wrapper, such as Cordova. You likely need a JavaScript framework, such as Angular or Ember. And you likely want a mobile UI framework, such as Ionic, Sencha Touch, or Trigger.IO.

Each mobile UI framework has different underlying requirements, so you probably want to start there with your research. Some incorporate their own native wrapper or have hard dependencies on Angular and Cordova. Each platform takes a slightly different approach and there is probably more than one right choice.

The competition between the platforms has really driven innovation and developer-friendly tools. However, with the constantly changing “best choice” development stack, finding an expert in developing one particular platform can be difficult.

What’s the Answer?

I hate to hit you with the same unhelpful answer, but it depends.

If you have in-house developers, the cost effective solution is to choose the technology that they’re able to develop or at least support following primary development. If you’re building for just one platform, I think the current answer is to go native. If your application needs a web browser presence, then you should go with a hybrid app. If your situation is more complex than these simple cases, you really have to research each platform and see if it is the right fit for your scope, budget, maintenance, and stability needs.

If you are unsure, let us know.  Our teams of developers can assess your situation, provide best practices and make recommendations for the best solution to meet your needs.

Digging In

  • Software Engineering

    When There’s Too Much to Fix: How Smart Prioritization Unlocks Revenue at Scale

    Every operations team has a backlog. The question isn’t whether you can clear it — it’s whether you’re clearing it in the right order. For most teams, the honest answer is no. And that gap between the order work gets done, and the order it should get done is quietly costing organizations millions. The Volume Problem High-volume exception processing shows up across […]

  • Software Engineering

    Creating Reusable Code Templates to Reduce Client Project Startup Time

    In consulting, one of the least visible but most expensive phases of a project is the beginning. Teams can spend days or weeks setting up repositories, agreeing on structure, wiring basic infrastructure, and solving problems that have already been solved many times before. Code templates are a practical way to reduce overhead while improving consistency. […]

  • Software Engineering

    Player Three Has Entered the Game: How AI Is Finally Bridging the Divide Between Design and Engineering

    As AI begins to become more prominent in our day-to-day lives, I find myself in a unique position. As a practicing software engineer and UI/UX designer, I am genuinely happy to see the introduction of AI tools begin to take shape in our industry. But more importantly, I am happy to start seeing the effects it is having on what has historically been a pretty challenging relationship: the […]

  • Software Engineering

    The Disappearing Middle of Software Work: Why the Bookends – Strategy & Impact – Matter Most Now

    Here’s a question nobody in enterprise software wants to sit with: what happens to the middle? Not the middle of the org chart. The middle of the work. The vast, expensive layer of effort that has defined enterprise software delivery for thirty years—translating what the business wants into working code. The requirements-to-implementation pipeline. The “build phase.” […]

  • Software Engineering

    Zero-Code Telemetry with OpenTelemetry’s OBI

    Full distributed tracing and exception capture for any application — without writing a single line of instrumentation code. View the source code on GitHub → The Premise Observability is essential for understanding what’s happening inside your services, but instrumenting an application by hand — adding trace spans, logging calls, and metric counters throughout your codebase […]

  • Software Engineering

    Building a Consultant in the Trenches: How Playing Offensive Line Shaped My Consulting Career

    People often ask me the same question when they find out that I played college football: “Do you miss it?” On the surface, it’s a bad question with an obvious answer. Yes. However, if I give myself a minute to sit with that question, the answer is more nuanced. Yes, I miss playing football, but […]