mrc's Cup of Joe Blog

Join us in exploring the world of modern development, evolving technologies, and the art of future-proof software

Mobile apps

Hybrid vs. Native vs. Mobile web comparison chart

EducationNative, mobile web, or hybrid? For companies considering mobile apps, that is the million dollar question. Which direction do you take?

The answer: It depends. There’s no single correct answer that applies to every situation. Each option (mobile web apps, hybrid apps, and native apps) has its own advantages. The right path for your company depends on a variety of factors, such as: What are you trying to accomplish with your app? When do you need it? Which skills do you have in-house?

Here are a couple of options to help you figure out which path is best: First, you can check out this white paper that takes an in-depth look at the topic. Secondly, we’ve put together the following comparison chart for each mobile development method. It compares the main differences, advantages, and disadvantages of each.

Build a web (and mobile) app in 30 minutes without programming

ProductivityIf your company plans on building mobile apps this coming year, or if you just wish there was a faster way to develop enterprise web applications, you should really try the newly revamped m-Power Trial.

The m-Power Trial was recently updated, and now also lets you build a mobile web app. In roughly 30 minutes, you will create an enterprise web app, along with tablet and smartphone versions of that web app. The best part: Everything is done without programming!

You can try it here: m-Power Trial

Mobile applications: Why architecture matters

Save TimeA couple of months ago, I wrote up my thoughts on developing mobile applications for business. In short, I believe that creating web apps designed for mobile use makes more business sense than creating platform-specific applications. I’d like to go one step further and explain how this concept works from an architectural perspective.

First, you must understand n-Tier architecture. While this sounds like a complicated technical term, I assure you that it’s relatively simple and makes sense from a business perspective. In short, n-Tier architecture breaks an application up into separate layers, or tiers. Typically, there’s a presentation layer (what you see in the browser), an application layer (your business logic), and a database layer (data storage). …