mrc's Cup of Joe Blog

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

7 hidden risks of native mobile app development

EducationAs more businesses build their own mobile apps, we’re seeing an increasing number of mobile app success stories crop up. For instance, here’s a recent article highlighting 4 different companies that use mobile apps to attract customers. Here’s another article from earlier this year highlighting other companies who are using mobile apps to improve business. I could share many more such stories, but you get the point: Mobile apps are taking off in the business world.

I believe this trend is on the rise. As businesses begin to understand the true power of mobile apps, many more will start building their own apps.

This is where things can get dangerous. Blinded by the possibilities, many businesses dive into mobile app development completely unprepared. They don’t understand the risks associated with mobile app development, and are headed for some unpleasant surprises.

Today, I’d like to help you avoid those surprises. I’m going to highlight a few of these hidden risks, with the hopes that you’ll be more prepared when you start the process.

But first, let’s quickly specify which type of mobile app we’re referring to. There are 3 different types of mobile apps (native/hybrid/mobile web), which you can learn more about here. However, today we’re focusing on the risks of developing native apps. Native mobile apps are downloaded via an app store/market and installed on the device itself. I’m addressing native apps because they’re probably the most popular application type, but also come with their fair share of hidden risks.

So, what hidden risks should companies watch out for when they dive into mobile app development? We posed that question to a few experts in the field, and have compiled their advice (along with some of my own) below. Here are 7 hidden risks of native mobile app development:

The 4 P’s of Business Intelligence Success

Education** This guest post was written by Estelle Nicholson. Learn more about Estelle in the author bio at the end of this post. **

When starting a BI project, your first step should be taking a quick look at existing initiatives and the overall culture and support for BI. Understand the “4 Ps” of “people, products, power and pilot” before you launch:

  1. Assess what you already have. Who are the people currently doing business intelligence activities? What roles could they play in a more formalized BI setting? Data experts, analysts, data set owners and compilers – all are key resources for requirements gathering and power use.
  2. What products and tools are people already using? Large data repositories, analytical software, spreadsheets, custom-built systems?
  3. Check your sponsorship or the power behind the mandate or the initiative.
  4. Engage influencers in a pilot early to demonstrate the capabilities of the tool(s) you’re implementing and build support.

7 web application development mistakes that kill usability

EducationNo web developer wants to create a bad user experience. Nobody sets out to make a confusing and frustrating interface that drives users away. But, the sad truth is…this happens far too often.

How often?

According to the online marketing institute, the problems caused by a poorly designed interface are substantial. The numbers indicate that:

  • 85% of users abandon a site due to poor design
  • 83% of users leave because it takes too many clicks to get what they want
  • 62% of users gave up looking for an item while shopping online
  • 40% of users never return to a site because the content was hard to use
  • 50% of sales are lost because visitors can’t find content

The fact is, usability is becoming an essential aspect of web application development. User expectations have changed. Modern end users expect to pick up a web app and understand how it works. Confusing interfaces will only frustrate users and drive them away.

However, many developers build applications which do just that. They unwittingly make development mistakes that hurt their web application’s usability. In doing so, they accidentally alienate their users.

What are these mistakes? In what ways do developers accidentally create interfaces that frustrate their users? We posed those questions to a few experts in the area of usability, and have compiled their feedback below. Here are 7 development mistakes that kill web application usability:

Weekly recap: Why big IT projects fail, a wake-up call for CIOs, and more…

EducationEvery week, I share the most interesting and useful tech articles that I’ve found over the past week. This week’s top articles focus on why big IT projects fail so often, a new look at the “native vs. mobile web” debate, and more. I hope you find them useful:

Smartphones: Business Risk or Opportunity
Business owners, CIOs, and IT leaders face a dilemma: How to harness the efficiencies of mobile devices while defusing the security risks. The fact is, many end users just don’t practice safe security habits. Those end users could very well compromise your company, unless you approach mobile the right way. My advice: The same thing I’ve said for the last couple of years. Treat the device like a thin client and use mobile web apps. This approach doesn’t store data on the device itself, and lets you keep your data safe behind your own firewall.

6 common IT practices that should be eliminated

EducationIn a past article, we explored the growing need for IT evolution and outlined 6 keys to a high-performing IT department. The fact is, keeping the lights on is no longer good enough. Modern IT organizations must move quickly, and drive the business forward.

However, I noticed a problem. While all of the keys outlined in that article will help IT departments improve performance, it ignores a critical issue: common IT practices that kill productivity and waste precious resources.

The fact is, you could follow each one of those points perfectly…yet still struggle. If your IT staff focuses its energy on time-wasting and resource-draining tasks, you’ll never drive the business forward. You’ll be caught in a never-ending cycle of being busy, yet ultimately unproductive.

So, what are these common time-wasting and resource-draining IT practices that must be eliminated? We posed that question to a few experts in the area, and have compiled their responses (as well as some of my own thoughts) below. Without further ado, here are 6 common IT practices that should be eliminated.

The dangers of choosing the wrong reporting software

EducationWhat’s the only thing worse than running a business without good reporting software in place? Running a business with bad reporting software in place.

The problems caused by bad reporting software can range from small inconveniences to major financial losses. For instance, bad reporting software can lead to:

  • Lost productivity
  • Wasted money
  • Security breaches
  • Flawed business decisions
  • and more…

How so? Take–for example–the most commonly used reporting tool: Spreadsheets. Why are spreadsheets a dangerous reporting option? Two reasons: They’re inefficient and dangerous:

Weekly Recap: 10 old-school IT principles that still rule, how to leverage BI for executive reporting, and more…

EducationEvery week, I share the most interesting and useful tech articles that I’ve found over the past week. This week’s top articles focus on how old-school IT principles have adapted with the times, how to leverage BI, and more. I hope you find them useful:

Four ways to leverage BI for executive-level reporting
While data is growing at a rapid rate, many don’t know how to turn this data into actionable insights. Why? It boils down to a lack of appropriate tools and processes.

6 critical guidelines for Business Intelligence beginners

EducationBusiness Intelligence (BI) consistently ranks as one of the top priorities in various CIO and IT surveys. A recent Gartner survey puts BI as the top CIO priority for the last two years running. Forrester comes to the same conclusion.

The fact is, many companies are (or are planning on) adopting a Business Intelligence solution for the very first time. With data growing by leaps and bounds, it’s no surprise that more businesses are looking for ways to capitalize on that data.

The only problem: Most BI implementations fail. It’s no secret. According to various surveys on the topic, anywhere from 60% – 80% of BI projects fail. Yikes.

This paints a grim picture. Implementing BI is the #1 CIO priority, and many businesses will start a BI project in the near future…but most BI projects fail.

Today, let’s explore a few ways to lower those numbers. What must companies who are new to BI do to ensure success? What critical tips should these companies follow? We posed those questions to a few experts in the field, and have compiled their advice (along with some of my own) below. Here are 6 critical tips for BI beginners:

Weekly recap: 9 hottest mobile development skills, strategic tech trends for 2014, and more…

EducationEvery week, I share the most interesting and useful tech articles that I’ve found over the past week. This week’s top articles focus on the hottest mobile development skills, Gartner’s strategic tech for 2014, and more. I hope you find them useful:

Combatting the information deluge
Information is exploding at an unprecedented rate. The burden falls on companies to not only turn that data into actionable metrics (like this user-defined dashboard, for example), but also secure and store that data.

5 new realities that developers must learn to accept

EducationWeb application development has changed. Driven largely by the rise of mobile and the growth of cloud-based applications and services, modern web application development is much different than it was just five years ago.

What’s changed? I classify these changes into two categories: Trends and realities. What’s the difference between a trend and a reality? A trend is optional. A reality is not. For instance, flat design is a trend. You don’t have to use it, but many people do. The rise of mobile users is a reality. No matter how much you may tell yourself otherwise, you can’t ignore the very real fact that smartphone and tablets are here to stay.

Today, let’s focus on the realities. How has web application development changed, and what new realities must web application developers learn to accept? We posed those questions to a few experienced developers, and they provided some excellent advice–which you will find below. Here are 5 new realities that developers must learn to accept: