mrc's Cup of Joe Blog

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

Education

Application modernization comparison chart

EducationHere’s a million dollar question: What’s the best application modernization method for your company?

Here’s the answer: It depends.

If your company needs to modernize existing legacy applications, choosing the best method varies largely on your needs, goals, and resources. You’ll need to answer a few questions before you begin, such as:

  • Why are you modernizing in the first place?
  • What’s your budget?
  • When do you need the job completed?
  • What do you hope to accomplish?

If you need help choosing the best modernization solution for your company, here are a couple of things that could help: First, here’s a free whitepaper entitled “Crash course in modernization,” that takes an in-depth look at the modernization basics. We’ve also created a handy little comparison chart, which compares 5 different modernization methods.

7 reasons why mobile web apps are better for business than native apps

EducationIf your business is planning to build native mobile apps, ask yourself this question: Are you building native mobile apps because you need to, or because you think you have to? While native apps are popular with consumers, they’re quite impractical for most businesses.

To understand why, let’s first look at why native apps are popular with consumers. Native apps do a couple of things very well: They deliver highly graphical interfaces and they’re easy to find and download. While these are important factors for consumers, are they really important to your business?

For most businesses, the answer is a resounding “No”. Unless your business needs highly graphical applications, mobile web apps simply make more business sense. How so? Here are 7 reasons why mobile web apps make more sense from a business standpoint:

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.

How to create home screen icons for your mobile web apps

EducationOne big difference between native apps and mobile web apps is how each one is accessed. Native apps are accessed via an icon located on the home screen or in the App drawer. Mobile web apps are accessed via the web browser. All in all, native apps offer simpler access by default.

Let’s fix that.

With minimal effort, your mobile web apps can offer the same ease of access provided by native apps. In fact, they will even look and feel just like native apps on your home screen.

Here’s how to do it.

7 things to look for in a web application development tool or IDE

EducationThe difference between good and bad development tools/IDEs is like night and day. A good development tool will reduce development time and turn anyone into a web developer. A bad development tool will cause headaches, restrict your options, and even harm the company.

With so many options, how can you distinguish the good from the bad before you buy?

The key to success is finding the development tool or IDE that provides the most options and the fewest limitations. While that decision is largely based on your company’s needs, here are 7 essential elements that you should look for in any development tool or IDE:

How to upload photos from a mobile web app

EducationHere’s a question for you: Suppose your company needs a mobile app that lets users upload photos from their current location. Does this job require the more difficult native approach, or will a simpler mobile web app meet your needs?

If you read the “6 ‘native’ features you can use with mobile web apps” article, you already know the answer. While file uploading sounds like a native-only feature, it’s actually very simple with mobile web apps. Today, I’m going to show you how.

How to use GPS in your mobile web apps

EducationHere’s something you may not know: Did you realize that mobile web apps and native apps are nearly equal in terms of capabilities? It’s true. As you learned in this article from a few weeks back, mobile web apps are much more powerful than most people think.

As promised in that article, I’m going to go through some of those “native” features and explain how to use them in your mobile web apps. Today, let’s take a closer look at the first feature on the list: GPS. Specifically, I’m going to show you how to use GPS in your mobile web apps, and also give you a few ideas on ways to use it.

Ready? Let’s get started…

5 big problems caused by bad application architecture

EducationApplication architecture is one of the single most important, yet boring topics you’ll ever run across. You’re not going to make too many friends at a party talking about technology stacks, open frameworks, or any other architecture-related themes. In fact, you’ll probably get a lot of blank stares wherever you talk about those things.

Yet, the difference between good and bad application architecture is mind-blowing. Good architecture is nearly invisible. Everything just works, it’s easy to maintain, and all of your applications operate in perfect harmony.

On the other hand, bad architecture is only invisible at the beginning, but becomes increasingly obvious over time. When you buy a new development tool or begin using pre-built software, the applications may initially work fine. But, if they’re built on bad architecture, problems will quickly arise. What exactly can you expect? Here are 5 costly problems caused by bad application architecture:

6 “native” features you can use with mobile web apps

EducationWhat’s the difference between a native app and a mobile web app? Let’s start with the basics. A native app is downloaded and installed on the device, while a mobile web app is accessed through the device’s browser. Native apps must be built separately for each platform, while one mobile web app works on every platform.

Following me so far? Now, let’s get into the confusing stuff.

What can a native app do that a mobile web app cannot do? This is where a lot of businesses seem confused. Many believe that mobile web apps are nothing more than a web page running inside of a mobile browser. They believe that native apps are the only way to fully take advantage of the mobile device’s hardware.

The truth is, mobile web apps are capable of much more than most people think.  What can mobile web apps actually do? I’ve created a list of 6 “native” capabilities that many businesses don’t realize are possible with mobile web apps.  Over the next couple of months, I’d like to write up posts covering each point in more detail, with examples and tutorials on how you can add these capabilities to your mobile web apps.  Sound good?  To start things off, let me first share the 6 “native” features that you may not realize you can use with mobile web apps: