9 Mobile Development Trends to Watch in 2019

Originally published January 23, 2018, updated January 29, 2019.

Mobile development is one of the most innovative and fastest growing sectors of the tech industry.

The average American spends over three hours a day on their smartphones (not including calls) and companies are pushing to gain a share of that time.

As mobile continues to work its way into daily life, the technologies rising to the top are ones that make that constant usage easier and more enjoyable.

It should come as no surprise that practicality, good user experiences, and convenience are the keys to winning public support in 2019.

Consumers expect their smartphones to do more than take calls and check email. They want more connectivity with the world around them, and they want that connection to be as safe as it is convenient.

To that end, here are the trends driving mobile developers in 2019:

1. Mobile Application Security

Users share more personal data with apps than ever before.

Mobile wallets have banking information, social media and habit trackers store details about personality and routines, and navigation apps keep records of everywhere a user goes.

At the same time, there’s enormous pressure to put apps out fast enough to keep up with consumer demand. Data breaches can be caused when companies rush development – and the risks are only rising.

The average cost of a breach was $3.62 million in 2017. Last year saw a 6.4% increase to $3.86 million.

In 2018 experts began tracking so-called “mega breaches”. These are cases where between 1-50 million records are breached, and they’re becoming more common as the Internet of Things (IoT) makes more user data available.

Alarmingly, 10 out of 11 of this type of breach are caused by malicious actors as opposed to technical errors. That shifts the focus from passively securing connections to actively preventing criminal intrusions.

In 2019, look for developers to emphasize security from the beginning of projects, with encryption throughout and automated testing at regular intervals. Artificial intelligence will also be on the rise for mobile security applications.

2. 5G Wireless Connectivity

2019 will bring the first major wave of 5G phones and wireless networks to urban areas. AT&T, which switched on their 5G wireless network in 12 cities last year, will add at least 7 more during 2019.

Sprint announced a 9-city 5G presence in the first half of the year with potential for wider coverage depending on how fast they can build out their infrastructure.

There were some test programs and small-scale rollouts from Verizon and AT&T last year, but without the right devices to handle it those haven’t done much more than raise excitement.

Now Sprint, Verizon, AT&T, OnePlus, and LG have all announced 5g-ready smartphones to be released this year.

Why is 5G so exciting? For one thing, it’s fast. 5G is at least 10 times faster than 4G.

Users will be able to download movies and apps in seconds rather than minutes, and streaming mobile video will be as fluid as watching at home.  C

arriers are warning that it’s only a little faster than 4G outside cities, but it’s still a major improvement considering how well it handles high-resolution media.

Latency is another major draw. 5G’s incredibly low latency- under one millisecond- will let multiple devices communicate quickly enough to respond to the real world.

Experts are primarily thinking of self-driving cars and drones, but the technology will also take mobile gaming to a whole new level of user experience.

5G is about more than smartphones, though. The technology is part of an overall shift towards improving the wireless infrastructure to support the growing Internet of Things.

5G could mean major advances for smart cars, self-driving vehicles, smart homes, Augmented Reality devices, wearables, and other mobile connected devices.

3. Accelerated Mobile Pages (AMP)

AMP is a set of protocols focused around HTML, JS, and a Google Cache that boosts the performance of mobile pages.

AMP-compliant pages load twice as fast as normal pages and perform well across a variety of devices and signal ranges.

With their higher availability and faster loading times, pages that use AMP have lower bounce rates and longer average session times.

Users also find AMP pages easier since Google places them in a special carousel at the top of search results.

That’s very tempting for companies looking to increase their site traffic (and who isn’t?).

There are some functionality limitations to AMP, but for basic pages those limits are outweighed by the speed and SEO preference.

Look for companies to continuing moving some of their customer-facing content to AMP throughout 2019.

4. Instant Apps

The barrier to adoption for a lot of apps is the download requirement.

People only have so much memory on their smartphones, and they hesitate to download apps that could just sit unused on their phones.

That’s not an unrealistic fear: only 20% of apps are opened again after the first use.

Surveys show that 75% of consumers feel more comfortable using apps with helpful reviews or screenshots, but Instant Apps take that a step farther.

Users can access them directly from the Google Play store without downloading.

Companies don’t need to build separate instant apps to take advantage of the trend, either.

Since they’re effectively features of an existing app (for example, the map section of a store app) which are used independently via a website, they use the same APIs and source code.

Developers only need to update their existing apps for Instant App functionality.

Instant apps offer some enticing benefits:

  • Instant apps open in seconds while the supporting website loads behind, giving the customer-facing impression of instant access.
  • Consumers can use just the feature they need or test-drive apps before downloading them.
  • Businesses can offload more functions (returns, coupons, and the like) to their app since customers can access them without having to go through the download process first.
  • Instant apps can be shared via links, which friends can view without downloading anything.

Early adopters have seen significant increases in full app downloads and engagement.

Updating for Instant App compatibility can take as little as a single day.

Instant Apps have become available on over 500 million devices worldwide since launching.

With satisfied customers including Vimeo, The New York Times, and the Wal-Mart owned shopping service Jet, it’s a sure bet that they will continue to rise in popularity.

5. Mobile Payments

Digital payment options are seeing a slow but steady transition to the real world. 2.1 billion consumers worldwide will use mobile wallets to make payments in 2019, a 30% increase from 2017.

Mobile payment has already become commonplace in China and India, where some stores accept nothing else.

Outside those markets mobile payments have been slower to grow, though they’re still gaining ground. In 2018 20% of Americans were using mobile wallets and payment options.

Experts predict that number to rise nearly 40% over the next year as mobile security improves enough to lend consumers confidence in the technology.

The leading general-purpose mobile payment systems in America are Apple Pay, Google Pay, and Samsung Pay. At least half of US retailers accept these, which makes it easier for consumers to leave their wallets at home.

Look for more brick and mortar businesses to begin accepting mobile payments. There’s also a trend towards loyalty programs with integrated mobile wallets that bears watching.

The Starbucks app’s mobile payment option saw over a million more users than Apple Pay in 2018, and over twice the number of Google Pay users. It will be interesting to see how this develops in 2019.

6. Mobile AI

Mobile AI is being fueled by edge computing and the rising demand for on-device processing.

A variety of mobile applications which were once unreliable are now maturing into enterprise readiness.

  • Conversational interfaces have improved along with advances in Natural Language Processing. Chatbots are leading the pack. In fact, 80% of businesses plan to release some kind of chatbot by 2020. Expect to see more chatbots and personal assistant AIs this year (especially on social media).
  • Recommendation engines are the power behind upsells at online checklists, but they’re also used in evolving applications like smart travel planners and health care apps.
  • Enterprise AI is a core component of digital transformation. Insights gained through enterprise analytics and predictive marketing will continue driving business in 2019 and beyond.

7. Wearable Devices

Technology has become a constant, reliable presence in daily life, and nowhere is that more obvious than with wearable devices. Users enjoy having increased control and persistent access to their data.

Most wearable devices on the market are smartwatches, with fitness trackers close behind. The category is broad, though.

New applications are constantly under development: wearable cameras, augmented or virtual reality headsets, and even smart clothing.

As a whole, the category is growing faster than predicted last year. It’s expanded from 84 million units in 2015 to an estimated 245 million units this year.

With companies like Apple offering products for a wide range of consumers and Google rumored to be working on a new wearable, this is definitely something to watch in 2019.

8. Augmented Reality apps

Although Augmented Reality has been tossed around for years, it’s coming into its own as a mainstream feature.

Both Google and Apple have released toolkits (Google’s ARCore and Apple’s ARKit) that make it possible for more businesses to take advantage of AR features.

The enterprise applications of AR are as varied as businesses themselves. One exciting use-case is the IKEA Place App.

IKEA has 411 stores in 49 countries, but for many people visiting a showroom still requires a road trip and significant planning. Enter IKEA Place, an Augmented Reality application that displays furniture at scale over a live camera image.

Users can then see how catalogue items will look in their home and whether larger furniture will fit. AR is seeing a rise in usage in fields like healthcare, engineering, and real estate as well.

Industry analysts predict that the AR market will reach $108 billion in revenue by 2020.

9. Beacon Technology

Beacon technology isn’t new. It’s been drifting around for a while in highly niche use cases, but it’s beginning to find its place as mobile technology becomes more advanced.

The idea of beacons is simple. A Bluetooth transmitter emits a signal visible only to compatible devices within a limited range. Smartphones with the right app can pick up that signal to receive timely, location-specific information.

Beacon locations are much more accurate than other locational data, which creates opportunities for more tailored interactions. Some examples:

  • Unlocking a hotel room as the registered guest approaches their door
  • Sending seat directions, game updates, and important alerts to fans within a sports stadium
  • Alerting loyalty club members passing a store of current sales

Since the technology has been around, what will expand in 2019 is the number of beacon-oriented apps for smartphones, wearables, and other connected devices.

Best Mobile App Development Company in Orlando

Concepta maintains their position as one of Orlando’s best mobile development agencies by creating dynamic technology solutions for modern business challenges.

Right now, that means staying on top of mobile trends.

Mobile development is one of the biggest enterprise priorities of 2019.

Companies need to be where customers are, when customers need them, and that means going mobile.

With that in mind, Concepta recommends investing in a right-sized mobile presence.  

It takes some planning, but sound mobile development is a solid path to winning new customers and improving the overall customer experience.

In the long run, that’s a competitive edge that pays off.

Interested in how these trends can help grow your business in 2019? Get a free consultation with Concepta’s experienced developers to explore your options!

Request a Consultation

Creating Fast, Reliable Apps with Cache API

cache-api

Progressive Web Apps (PWAs) are leading the charge in providing mobile access at a relatively low price point.

They have a lot of advantages over hybrid apps and bypass the “download barrier” of native apps altogether.

PWAs operate within browsers, which imposes some limitations. One of these is the browser’s built-in cache.

Mobile apps rely on caching to stay operational in variable signal strength areas, and the browser’s native cache is too unreliable to provide the best possible service.

There is a tool smart developers use to give PWAs – and other applications- a performance edge: Cache API.

The Power of PWAs

PWAs are hosted by a website and accessed through a device’s browser. The most obvious benefit is that there’s no download required.

Users simply navigate to the app, grant permission for limited device access, and are granted full access to the app’s features.

That isn’t the only reason for their popularity. As a mobile option, PWAs offer better user experience than responsive mobile sites without the higher cost of standalone apps.

They’re fast, secure, always updated, and have the native look and feel that appeals to users. They can access a growing array of device features.

PWAs also work anywhere. After the first load, users don’t even need to be online.

The app can store information for automatic update when the connection is restored – which is why reliable caching is so important.

Introducing Cache API

Cache API is a system that securely stores requests and responses via JavaScript that can be accessed anytime. It can use service workers to cache network requests so the app is usable offline.

The API also serves as general storage, able to store almost any kind of response without worrying they’ll expire.

Caching things like this decreases traffic and network activity. It boosts the application’s performance, which is a major benefit when user experience weighs so heavily in repeat purchase decisions.

Cache API Vs Browser Cache

It might seem like using Cache API when there’s already a built-in browser cache is a waste of time, but there are good reasons to use Cache API in addition.

First and foremost is control. Developers who choose Cache API can implement custom cache control logic.

They can set priorities for what remains in the cache and what can be purged to make space. The browser cache only purges based on storage requirements.

This feeds into another benefit: reliability. Cache API adds a layer of dependable control that’s missing from even the better modern browsers.

Chrome and Firefox have been working to improve their browser caching, but it still needs improvement. A Facebook study found that only 25% of what they expected to find in the cache were actually there.

As a technical advantage, when users refresh a PWA their browser skips the HTTP cache. Service workers set up with Cache API always intercept requests.

It’s also useful that Cache API can cache multiple requests when the PWA is first run. Even those that haven’t been accessed yet can be stored.

Having these ready speeds up later requests even as the user moves through low signal areas.

Looking At Limitations

Cache API has a few notable limitations. Some browsers require use of https to access the API. Size can be a problem, too, since each browser has its own storage limits that need to be addressed.

Developers can manage this using cache quota usage estimates found through the StorageEstimate API.

Compatibility is another issue. Browser support for PWAs is growing but not consistent, and not all browsers support this feature. That does seem to be changing.

Cache API can be used in Chrome, Opera and Firefox now, and Edge and Safari have reportedly marked it as “In Development”.

Final Thoughts

With a simple API and a little javascript, applications can be given an amazingly functional caching layer that improves their performance while decreasing bandwidth usage.

It benefits users and servers alike. Given these benefits, Cache API should be on the technology short list when it comes to building PWAs.

Orlando Mobile App Development Company

Having a user-centric mobile presence is a critical part of modern digital strategy, and it doesn’t have to break the bank.

Concepta, a leader in Orlando’s mobile development industry, has years of experience working with companies of all sizes.

We’ve created solutions for partners ranging from Kingdom Strollers to Disney themselves.

 To learn more about mobile technology that meets your company’s needs (including your budget), set up a free consultation with one of our experienced developers.

Request a Consultation

The Best JavaScript Frameworks for Mobile Development

javascript-frameworks

JavaScript frameworks are great tools for building mobile apps. They’re efficient, lower development costs, and tend to have the security benefits that come with large, active communities of developers.

Deciding to use a framework is an easy choice. The harder question is, which framework fits the project at hand?

Here’s Concepta’s take on four of the best JavaScript frameworks for mobile development.

jQuery Mobile

This lightweight mobile framework is based on the popular jQuery library. Developers use jQuery Mobile for mobile website development as well as apps. It’s touch-optimized with a focus on broad compatibility (Android, iOS, Windows Phone, and Blackberry).

Eliminating cross-browser issues is one of jQuery Mobile’s biggest draws. The framework supports a huge variety of platforms, devices, display sizes, and screen resolutions. There’s no need to use a device-specific programming language. Instead, developers can use standards like JavaScript, HTML5, CSS3, or AJAX.

Designing is simplified with the ThemeRoller customization toolkit. ThemeRoller offers a lot of tools that make editing themes easy, including drag and drop color and component changes. There are plenty of options for manipulating page layouts, headers and footers, and other design details.

Limitations

While jQuery Mobile makes it possible to perform complex scripting operations with little code, there are drawbacks. Performance varies by device. For example, jQuery Mobile apps lag noticeably on Android but run more smoothly on iOS.

Although the framework can outperform other mobile websites, it doesn’t outperform native apps. jQuery also lacks the full access to device features offered by other mobile app development tools.

NativeScript

NativeScript aims for a “write once, use everywhere” philosophy and comes very close. It’s an open-source framework for building Android, iOS, and Windows apps. With access to native API, it creates applications that behave like native apps on those platforms. Heavy code reuse between platform versions cuts the overall development time, too.

The framework supports the use of Angular, Vue.js, TypeScript, and Javascript. There are hundreds of NativeScript plugins, but developers aren’t limited to that toolset. They can integrate Node Package Manager, CocoaPods for iOS, and Gradle for Android.

Being open-source and free lowers the cost of working with NativeScript. Companies see extra savings through shorter development timelines.

Limitations

NativeScript aims for native performance. In practice, though, users experience some lag when opening apps. Also, critics point out that there are many inefficiencies in the NativeScript core that make debugging unnecessarily complicated.

It’s worth noting that plugins aren’t 100% verified and vary widely in quality. An inexperienced developer could accidentally introduce a vulnerability if they aren’t careful to check every plugin before use.

React Native

Facebook created this cross-platform native app development tool for its own use before releasing it to the public in 2015. Like NativeScript it features heavy code reuse, though the philosophy here is “learn once, write everywhere”. Once the tools are learned they can be applied to any platform.

React Native provides the native performance missing with NativeScript. It renders native UI elements for a “true to platform” feel that appeals to device loyalists while being less expensive to develop than a native app.

Real-time reloading leads to a smoother, more responsive development process where users can get faster feedback on changes as they work. This is one of the developer-friendly aspect of React Native that attract its large, active community of developers.

Limitations

Despite matching native apps in performance, React Native doesn’t fully support all native features yet. Users have to wait for Facebook to add those capabilities. There are generally fewer specialty and custom modules than some frameworks, as well.

The different design styles of Android and iOS will result in unpolished apps if a designer isn’t careful. Navigation is sometimes a little irregular regardless of skill.

Aside from technical considerations, some developers are wary of being totally reliant on Facebook. All signs point to a long future for React Native and Facebook is still putting resources into it, but the platform does still own the license and can theoretically revoke it.

PhoneGap

PhoneGap is a hybrid app development framework that is open source version of Apache Cordova. Users can build for multiple platforms with a single codebase, writing in HTML, CSS or JavaScript. Apps built with PhoneGap have decent access to device hardware. There are allowances for offline capabilities as well.

PhoneGap has a healthy library and a robust backend that makes development fast and easy. Developers don’t need specialty skill sets to use it; web development skills will give them access to all the framework’s features. Those qualities combine to make it a great tool for rapid prototyping on a budget.

Limitations

PhoneGap doesn’t offer a lot of UI widgets, but performance is far and away its biggest limitation. It suffers from noticeably lower performance than other frameworks.

Making the call

There’s no single framework that’s best in every case.

  • PhoneGap is great for rapid prototyping, but the performance issues may frustrate end users in the long run.
  • React Native and NativeScript take opposite approaches to cross-platform development which should factor into their choice for a specific project.
  • jQuery provides slightly lower performance but much wider compatibility, making it useful when end users can be expected to access the app through many kinds of devices.

Try not to go into a project with a favorite framework in mind. Look at the specific needs of the app, consider its purpose and who the end users will be, and discuss options with an experienced developer.

The wrong framework can lead to a frustrating, “square peg in a round hole” development process. The right one saves enough time and money to make it worth a little extra forethought.

Mobile Development Company in Orlando

As one of Orlando’s most renowned mobile development agencies, Concepta has a collection of clients who need fast, economical development.

Our developers stay on top of emerging JavaScript frameworks to be sure they have the right tool for any job, whether it’s building a client-facing app for The Learning Company or a sales portal for Anago.

Getting ready to build your next mobile app? Concepta has more than a decade’s experiences building dynamic enterprise apps for everyone from state-wide chains to national celebrities. We can guide you through the JavaScript frameworks that will help you meet- and beat- this year’s business goals. Reserve your free consultation today!

Request a Consultation

Why you should (or shouldn’t) use React Native

use-react-native

React Native is a powerful platform for building cross-platform apps that have the native look and feel users love, though it can struggle with CPU-intensive tasks.

Perfect cross-platform development is a hot topic in the software world. It’s essentially El Dorado: everyone argues about whether it really exists, and if anyone were to discover it they’d be rich beyond their wildest dreams.

Hybrid solutions are closer than ever- but they still can’t compare to the performance and reliability of native apps.

Enter React Native, a relative newcomer that aims to live up to the “write once, run everywhere” promise. React Native apps are native apps, just built using a different toolset, and their popularity is booming with developers and businesses alike.

Of course, while React Native is an incredible and promising tool it isn’t the long-awaited “map to El Dorado”. There are still limitations when it’s held up against native apps.

Read on to explore the power of React Native, find out where its limitations lie, and decide where it fits in a modern enterprise technology stack.

What is React Native?

React Native is a framework for building natively-rendered mobile apps using ReactJS, a JavaScript code library developed and maintained by Facebook.

The framework’s main selling point is its ability to create cross-platform apps that provide a much better user experience than the current hybrid options on the market, closer to that of native apps.

The Case For React Native

React Native takes a different approach than other hybrid and mobile web models. Instead of trying to simulate native performance, it takes actual native user interface (UI) building blocks and assembles them with React’s special brand of JavaScript.

Because these are the same building blocks iOS and Android use, React Native apps render like native apps. They have the same native look and feel device loyalists expect.

Developers have the option to write and embed custom native code, as well as writing in a mixture of native and React to get the exact function desired while maintaining the native appearance.

Native rendering is a huge benefit. Besides the obvious boost to user experience, it gives React Native a host of additional perks.

Cross-platform development

With React Native, one codebase runs on iOS, Windows, and Android. Only a small portion of the app needs to be customized for each operating system. It provides faster, more reliable performance than hybrid or web apps, too.

Development Speed 

In theory developers build their code once, in JavaScript, and React Native takes care of creating platform-specific versions. In reality the translation between operating systems isn’t perfect, but there’s still a huge chunk of the codebase shared between platforms.

That cuts development time for an app by as much as half while still supporting multiple platforms. If there’s already a web app, much of that code can be used with React Native to trim development timelines even more.

Developer productivity

React Native is a dynamic toolset with a lot of productivity features, like integrated components that provide “shortcuts” to common tasks. The framework also uses hot reloading, so developers don’t have to recompile the entire app every time they make a change.

Besides playing a role in React Native’s fast development speed, these features create an enjoyable, productive developer experience. Cutting out unnecessary interruptions helps developers stay engaged, which leads to better end products.

Cost

There are clear savings in both time and money when one app can be repurposed to cover all devices. There are fewer overall development costs and a lower up-front investment. Maintaining one code base lowers long-term maintenance expenses.

Even when the additional code to tailor the app for each operating system is considered, there’s much less work involved than in building multiple independent native apps. Plus, more efficient development means that the single React Native app is done sooner than comparable apps.

Add in the shorter time to market (and the ability to begin working towards ROI) and it’s easy to see how the savings add up.

The Case Against React Native

There’s a strong argument to be made that React Native comes closer to mimicking native apps that any of its current competitors. The idea to use natively-rendered components is an innovative approach with a lot of promise.

However, there are tradeoffs involved in making it work that mean React Native apps still fall short of native ones. Here are the major issues critics have with the framework:

Performance

The number one drawback to React Native is performance. It is better than other hybrid tools and web apps, but there’s no getting around the large overhead framework that slows down performance when measured against native apps.

For straightforward, simple apps and proof-of-concept work, the reduction in performance isn’t noticeable enough to have a huge impact. Using React Native for anything more complex could mean taking a hit to user experience.

“Reusable” codebase

As mentioned earlier, the “write once, use anywhere” motto isn’t entirely accurate. Developers have to configure the app for each platform. The size of that extra bit of code depends on the app’s function and the relevant operating system (some are more React-friendly than others).

In practice anywhere from 60-90% of the codebase can be fully shared. Although this still cuts development time by a significant amount, it does mean React Native isn’t a perfect platform-agnostic solution.

Size

React Native apps are bigger than native apps. This has a few unfortunate side effects. Users with older or economy model devices might not be able to handle it.

Those in developing markets often don’t have reliable access to 3G networks, so downloading large apps takes too much time. Finally, customers don’t like to use all their device storage on apps.

They might not download a large app, and when they start to run out of room for photos larger apps are the first to get deleted. Good developers have a few tricks for reducing the size of a React Native app, but it’s still something to keep in mind.

Quality Assurance Issues 

Debugging React Native gets complicated. Apps can be made with a mixture of custom native code, third party plug-ins, and regular React Native components.

It takes experience to navigate the app when tracking down the source of a problem.

Growing pains

The downside of being new and innovative is that React Native still has maturing to do. Facebook is actively tweaking and updating in response to user feedback, but they tend to be slow to update the software development kits (SDKs) when Android or Apple does.

Also worth mentioning is that as a younger tool, the documentation isn’t as user-friendly as it could be. It varies between highly dense in some places and too loose to be helpful in others.

That’s something that will ease over time, but right now it can be a hassle. New third-party libraries springing up are a mixed blessing: they offer more options for shortcuts but can introduce vulnerabilities into an app if they aren’t vetted carefully.

Exploring Alternatives

Looking at alternatives is a useful way to define a project’s priorities and decide whether React Native is the best fit. Here’s how it stack up against other formats:

  • Native apps: Native apps are the only practical option for graphics- and processing-intensive apps. They outperform every other type of app on the market. It takes time and money to build native apps, though, and most enterprise apps don’t need that level of performance to be successful.
  • Hybrid apps: Hybrid apps are essentially web apps with a native “wrapper”. They have the same advantages as React Native when it comes to development speed and cost savings. However, most hybrid apps can’t fully access device hardware, and their UIs don’t have a native feel.
  • Progressive Web Apps (PWA): PWAs operate within a browser. They can be given the feel of a native app and even can access some device features with the user’s permission. Their biggest draw is that users don’t need to download anything before use. On the flip side, PWAs don’t have full device access and use battery faster than other app formats. Without an app store presence they suffer in mobile search rankings, too.

use-react-native

Making the Call

When used for an app that plays to its strengths, React Native is a serious force-multiplier. It enables faster development, more responsive update cycles, and that all important “native UI” feel that consumers respond to.

It’s simple to build a basic, flexible app and scale it as usage grows. A lot of major players (besides Facebook and Instagram) use React Native in their apps, including:

  • Walmart
  • Airbnb
  • Wix
  • UberEATS
  • Soundcloud
  • Skype

Used outside its strengths, however, React Native adds an unnecessary layer of complexity. Developers unfamiliar with it can wind up with a large, convoluted, hard to manage codebase.

It isn’t well-suited to CPU-intensive apps, either. Trying to substitute React Native where a truly native app is needed leads to performance issues and the resulting degraded user experience. (It should be noted that a growing number of lighter VR/AR apps are being built with React Native, so the lines are blurring.)

Making the call on whether to use React Native depends on the app at hand. As a general rule it should be considered for projects where user experience and budget are equally important and when development speed is critical.

It should be ruled out for apps that are expected to be CPU-intensive (which is still the wheelhouse of native apps) or where the download barrier is a major concern (which might be better suited to Progressive Web Apps).

Best Mobile App Development Company in Orlando

When in doubt, consult with an experienced developer.

Orlando mobile development leader Concepta has experience with working with some of the biggest names in various industries to help them overcome business challenges, grow sales, and improve processes.

They know that each problem calls for a specific solution.

For example, the solution Concepta created for Kaluah Tours was very different from the one they built for FEMA (and vice versa).

Consultations take time, but they’re worth it. React Native has a host of benefits to offer if a specific app does fall within its “sweet spot”.

Are you ready to harness the power of React Native? Set up a complimentary appointment with one of Concepta’s developers to upgrade your mobile presence today!

Request a Consultation

Google Mobile-Friendly Test: What You Should Know

google-mobile-friendly-test

Originally published Jun. 16, 2015, updated Aug. 23, 2018.

It’s 2019, and mobile development is shooting to the top of everyone’s priority list (if it wasn’t already there). A strong mobile presence is absolutely mandatory for companies who want to stay competitive.

Consumers now spend most of their media time on mobile, and 92% of those who search for something on their smartphone will make a related purchase. Even local businesses need to go mobile: 78% of local searches result in a purchase within 24 hours.

There’s also the matter of search rankings. 67% of site visits go to the top five search results, and only 5% of searchers click to the second page. Businesses need to win those higher rankings to attract eyes to their pages.

That won’t happen without being mobile friendly, at least not since Google updated their ranking criteria to analyze mobile sites before desktop.

Enter the Google Mobile-Friendly Test. If your mobile site can’t pass it – or worse, you’re still using flash- you’ll potentially be losing out on the 96% of mobile search traffic driven by Google. Here’s what you need to know to stay on top.

What is the Google Mobile-Friendly Test?

The Google Mobile Friendly Test is a tool that allows companies to type in their URL and find out how mobile-friendly Google thinks their site is. It measures how easily users can access, read, and navigate the site on mobile devices, with a pass-fail score and suggestions for improvement.

google-mobile-friendly-test

Google drew a lot of ire from developers for inaccurate failing grades after the test’s launch in 2015. Critics pointed out that the tool had a hard time understanding JavaScript and would downgrade pages that loaded quickly on technicalities.

Google responded with a series of updates, including one in early 2018 that vastly improves the way the test handles JavaScript sites.

What Does It Look For?

In order to be considered mobile friendly, a website needs to load quickly and evenly across a wide range of devices and signal conditions. The Google Mobile Friendly Test looks for issues that prevent this, such as:

Flash

Most mobile browsers don’t support Flash. Because mobile users won’t see that content, they can’t access the full site.

Viewport issues 

If the viewport isn’t configured to adjust for screen size or is fixed-width, it won’t display properly on all mobile devices.

Horizontal scrolling

This is not a natural movement. Vertical scrolling has become the standard on mobile, as well as desktop.

Content doesn’t scale

Mobile sites shouldn’t be identical to desktop, but smaller. The content should adjust to the screen size when viewed on mobile.

Unsuitable font or text

Text should be clearly legible on a small screen without zooming in.

Touch elements are too close

Buttons and links should be far enough apart to be easily usable by human fingers without the risk of accidentally hitting the wrong link.

google-mobile-friendly-test

Alternatives to the Google Mobile Friendly Test

Google’s tool is one to watch, since it reveals how Google sees the site. However, there are other popular tools that help fine-tune a site’s mobile performance.

  • BrowserStack: This powerful tool for testing mobile design creates screenshots of how a page looks on every device. The downside is that it loads a little slowly. Also, it’s a paid service (though it offers a lot of features for the subscription price).  
  • Keynote MITE: The free version of MITE offers a grade, like the Google Mobile Friendly Test, while higher subscription levels have an expanded suite of tools.
  • W3 MobileOK Checker: Free and open source mobile tests will always have a place in development. This one not only identifies problems but separates them by severity and category.

Dealing With A Failing Score

A “not mobile-friendly” rating should be a wake-up call. It doesn’t just mean the site won’t rate well. It means visitors who DO get there will have a bad experience.

Users are five times more likely to abandon a site that isn’t optimized for mobile. Worse yet, because most mobile searches have timely intent, an unoptimized site can funnel customers straight to mobile-friendly competitors.

Mobile App Development Company in Orlando

Take the list of issues from the Google Mobile Friendly Test (and any other tools used) to a dependable developer as soon as possible.

Concepta, a renowned Orlando mobile development agency, has a decade plus experience solving technology problems for clients.

We can help redesign the site to provide a faster, more responsive experience for mobile users – and keep those users from switching to competitors.

How mobile friendly is your site? Concepta’s developers can talk you through your GMFT results and suggest other mobile-friendly technology like Progressive Web Apps. Set up your free consultation today!

Request a Consultation

Mobile Enterprise Series: Native Mobile Apps

native-apps-enterprise

Hybrid mobile apps have come a long way, but native mobile apps are often seen as the “gold standard” of mobile apps. As actual downloaded software they offer more functionality than the current breed of hybrids.

There are even times when they’re the only practical option for an app. User experience is growing in importance, and native apps definitely deliver in that area. Still, there are limitations to be aware of before investing in native.

What It Means to Be Native

A “native mobile app” is built for a specific platform (Android, iOS, or Blackberry) using that device’s specific programming language. iOS relies on Objective-C or Swift, for example, while Android favors Java and Blackberry uses C++. These apps are downloaded from an app store or another hosting location and live on individual devices.

The Power of Native

Native apps have a lot of advantages over other formats.

Performance

Because they’re written for a specific device, native apps have none of the compromises developers have to make when building hybrid apps. They open faster, handle data-intensive or complex functions well, and generally have superior performance.

Access to device functions

Native apps can potentially access all a device’s functions, whether they’re hardware or other apps. This includes the camera, microphone, flash, compass, accelerometer, gyroscope, calendar, alarms, phone book, and any other feature the user allows. They also offer push notifications. With up to a 65% open rate, push notifications are incredibly useful for keeping users engaged with an app. Hybrid apps can reach more device functions than ever, but they have structural limitations when it comes to full access.

Reliability

Offline access is in demand, especially in emerging markets and for business travelers. Since they live on a device, native apps have excellent offline potential. Users can access selected functions outside of a coverage area with the assurance that the app will update once the connection is restored.

Availability

Device specific development means better compatibility, so native apps are less prone to failing. They have a relatively high rate of availability when compared to hybrid or web apps.

User experience

Reliability, speed, and availability combine to create a high quality user experience. Plus, native apps use familiar device conventions that make navigation and trouble-shooting intuitive for fans of the platform.

Found in App Stores

The first hurdle in enticing users to download an app is helping them find it in the first place. When it’s in the app store, it turns up in searches by customers looking for similar apps. Potential users can view ratings and reviews from current users, which has been shown to increase consumer confidence. There’s also the peace of mind inspired by an app’s presence in the App Store since there are quality guidelines imposed by the App Store itself.

Better vendor support

Building an app is a significant investment for companies. Native apps have more assurance of long-term vendor support. They offer platform-specific Software Development Kits (SDK) that make development easier and increase the final quality of the app. Stability like this can be a major draw during a hectic digital transformation process.

Limitations of Native Mobile Apps

If there are so many advantages to native apps, why aren’t all apps native? There are some unavoidable drawbacks to native apps.

Cost

Native apps are more expensive to develop and maintain. They have a longer development cycle that needs a team of platform specialists. Because they only work on a single device, companies that choose native must build a different app for each platform they plan to support. This is potentially a serious problem for creators of enterprise apps.

App Store approval

Being in the App Store reassures users for a reason. The approval process can be complicated, and there’s no guarantee that an app will be accepted at all. While it’s not an everyday problem, changing guidelines can result in last-minute changes to what was a finished app.

Download barrier

Users need to download the app to use it. The average American downloads one or two apps a month, so competition for device space is fierce.

Support issues

When users are working on different devices, app support and customer service become complicated.

When Native is the Best Choice

Despite the higher cost, there are times when only a native app can handle the project at hand.

If connectivity expected to be an issue, few hybrid models can match native offline performance.

Games and other processing-intensive apps need the better performance of native to provide the kind of user experience that keeps retention rates high.

Also, when an app needs to use a lot of specialty hardware features native is the logical choice.

That applies to cross-app interactions (when the app needs to access other apps like calendars, alarms, and contacts) as well.

Native apps translate into performance. Hybrid apps have many useful applications and there are many use cases where the difference in speed is negligible, but it’s important to know when there’s no substitution for native.

Orlando Mobile App Development Company

The final call should be based on recommendations from a reputable mobile developer. A loyal, varied customer base is a strong sign of a good developer.

Concepta, a leader in the Orlando mobile development market, has experience with international lending companies like Service Finance and regional tourism businesses like Kingdom Strollers.

Having a diverse group of satisfied clients demonstrates a sound understanding of technology as well as a commitment to building long-term relationships over making maximum profit on a single project.

At the end of the day each app needs to be taken on a case by case basis.

Consult with a developer, discuss options with stakeholders, and make the decision based on long-term business needs even if that does call for a larger up-front investment.

After all, the cost of building an app that doesn’t work is always higher than investing in a native app.

Trying to decide between a native and hybrid app? Bring your questions to Concepta’s development team. We can provide tailored advice with your specific business goals in mind. Consultations are free, so schedule yours today and take the first step towards a successful release!

Request a Consultation