Interesante. La era Post-App Móvil. Mobility is about to enter the post-app era, says Gartner

At an event in South Africa, Gartner analysts look ahead to an era of mobility that goes beyond apps

As the convergence of devices, bots, things and people accelerates, businesses will need to learn how to excel at mainstream mobility, as well as prepare for a post-app era, according to analysts at Gartner.

Speaking at a symposium in South Africa, Gartner vice-president and distinguished analyst David Willis laid out his version of a possible future for the mobile world.

Willis said although users would continue to use mobile apps, the overall importance of apps in terms of delivering services would begin to diminish in the next few years, and bots and virtual personal assistants (VPAs) will begin to replace some app functionality.

“The post-app era means that there will be more data and code in the cloud and less on the device, thanks to the continuous improvement of cellular network performance,” said Willis.

“The post-app era will be an evolving process through 2020 and beyond. It has already begun and organisations should prepare for it by being agile and tactical, planning for new skills, assessing the opportunities created by the post-app era, and developing a digital business strategy that integrates different technologies.”

A driving force behind the move to models of mobility that are less reliant on apps will be the anticipated growth of the internet of things (IoT), said Gartner.

Willis predicted with bring your own device (BYOD) and bring your own application (BYOA) becoming the norm for the majority of organisations, a new trend – predictably dubbed bring your own thing (BYOT) – will emerge, and it will help introduce some of these new interaction techniques and platforms that will dilute the need for dedicated apps.

According to Gartner, in the next 18 months a quarter of new mobile apps will be able to talk to IoT devices. For now, said Willis, an app or browser will be the preferred mode of communication between an IoT device and a smartphone, but it will quickly be challenged by a number of trends and emerging technologies.

Fuente: Mobility is about to enter the post-app era, says Gartner

HTML5 vs. Native: The Debate Is Over

This editorial covers the pros and cons of HTML5 and native mobile app development. See how native app development can give you an edge.

Marketplace analysts and mobile strategists love telling us that the debate of HTML5 vs. local apps is highly overstated.  What’s more important is the general approach, they say. The readiness of your enterprise systems for mobile. The supply of mobile talents. The options of your improvement groups. The fee/gain analysis, etc.

But from what we’ve seen, the debate is pretty much over. While HTML5 has made good progress within the past few years, and while app builders still cite HTML5 as their most-used mobile platform (understandably, given their generic ability units!), the market definitely dictates the selection of native mobile structures.

Customers Decide on Local Apps

Studies indicate that mobile experience has a massive effect on how purchasers view an emblem and interact with it. Oracle recently had a look at has discovered that more than half (55%) of surveyed customers said a bad app might put them off using a company’s services or products.

If you are a consumer-targeted, market-pushed company, probabilities are that your customers have already spoken — and you’ve taken notice.  What we see again and again is organizations choosing an HTML5 or hybrid app and getting bitterly disenchanted with their customers’ reaction. The organizations who put out local apps, on the other hand, have an immediate, aggressive advantage.

Working example: Delta’s native Fly Delta app and its superior overall performance vs. its competitors’ web-based apps. Customers who fly often depend upon consumer-pleasant native features to quickly get records, submit itinerary modifications, and more.  Web (HTML5) apps clearly do not offer the easy experience local apps are well-known for. Domino Pizza, likewise, dazzled users with its overhauled local app, leaving its competition to play catch-up.

Why Do Local Apps Stand Out?

Allow’s look at some variations between the dominant mobile strategies currently in play in establishments.

Cell Website

Pros:

  • A brief choice for making existing content available via a mobile tool.
  • Simplest needs to be built once and could be usable for every tool.

Cons:

  • Inferior user experience: Users anticipate their mobile apps being specific: a compelling person interface; unique functions taking benefit of mobile device hardware; applicable push messaging. Those are notably limited with mobile websites, which are commonly supposed to genuinely show information.
  • Inferior performance: Prolonged load instances and incapability to feature in offline or low-bandwidth mode may be a prime turnoff. In line with Flurry, mobile users spend 86% of their time on mobile internal apps rather than in the browser.

HTML5 or Hybrid Mobile App

Pros:

  • A mobile app built with HTML5 or comparable technology can come up with the ‘area’ on a consumer’s mobile phone that can be used to bridge some of the gaps among native apps and a mobile website.
  • HTML5 or hybrid (wrapped) apps are an appealing route for teams that have Internet development capabilities and want to build mobile apps to provide extra engagement.

Cons:

  • An HTML5 app is, basically, a mobile website wrapped in ‘sheep’s clothing.’ all the UX/overall performance issues mentioned above will nonetheless follow. As those apps require a constant net connection, they restrict the customers’ functionality to utilize them in low/no bandwidth areas.
  • Those apps could be built with the exact same feature for every tool; without a unique function that customers have come to expect in a mobile experience.

Facebook CEO Mark Zuckerberg has stated that making a bet on HTML5 became his biggest mistake with mobile.

Native Mobile App

Custom, native mobile apps offer excellent consumer enjoyment with the most functionality.

Pros:

  • Rich, clean UI.
  • Use of cutting edge device talents.
  • Faster load instances compared to web apps.
  • Sturdy performance in online or offline.
  • Higher discoverability.
  • Superior security in comparison to HTML5.

Cons:

  • Require improvement for each mobile platform.
  • Local improvement capabilities are expensive!

Fuente: HTML5 vs. Native: The Debate Is Over – DZone Mobile

How to Select App Development Frameworks: Native vs. Web vs. Hybrid

When selecting frameworks with which to build apps, the biggest consideration is what kind of apps organizations plan to deliver: native, Web, or hybrid.

As companies start to build their own mobile apps, they’ll have to choose app development frameworks.

It’s an important first step to take an existing process and make it accessible from a mobile device. But apps become transformative when they take advantage of the rich features a mobile device can provide, such as location-based services, push notifications and seamless data sharing. When selecting frameworks with which to build these apps, the biggest consideration is what kind of apps organizations plan to deliver: native, Web, or hybrid.

Native App Development

Building a native application always results in the best user experience. Mobile operating system makers invest heavily in their own development tools. They want to make sure that the apps developers write in their native languages can take advantage of all the latest OS features and perform at their best.

Companies that have no prior experience with mobile development may be hesitant to have their developers learn separate languages to write apps for both Apple iOS and Google Android, however, because of the extra effort required to support multiple OSes. In situations where a company is standardized on one OS or requires tight hardware integration — such as with embedded devices, kiosks, point of sale and other special company-issued devices — it may be more important to develop native applications.

Browser-based Web Apps

At the other end of the spectrum are Web apps that users access in mobile browsers. Developers can write these with more familiar Web technologies, such as HTML5, CSS, and JavaScript. One version of a Web app can run on multiple mobile OSes. In addition, advances in HTML5 mean Web apps can now do many of the things that native mobile apps can, such as take advantage of cameras and geolocation and launch other apps on the device from within the Web app.

They’re attractive, but browser-based apps have many drawbacks. It’s only possible to send users push notifications with a few specific browsers, and app logins and sessions can expire quickly. Plus, Web apps can’t take advantage of all the latest OS features — some of the most unique and important traits that make mobile apps so valuable.

For all these reasons, mobile browser-based Web apps have limited use cases in the enterprise.Another problem: Web apps are just less convenient than native apps. Users have to remember how to navigate them, dig into bookmark menus to find them or know how to place Web bookmarks on their home screens. IT administrators can push these bookmarks to devices with mobile device management, but they still require different management processes than other apps.

Hybrid Apps

Hybrid apps are Web apps that run inside of a native app shell. Conceptually, this approach brings the best of both worlds. Developers can write the core logic of the app in a Web-based language that’s portable across multiple mobile platforms, and the shell can use native code to interact with the device’s unique features. As a result, IT can manage and deploy a hybrid app just like any other native app.

Hybrid apps can be as simple as a Web page embedded inside a native app, or they can be much more complex. Many app development frameworks can take apps developers write in Web-based or other languages and compile them into complete native apps for different mobile OS’s. Some app development frameworks provide only the user interface for hybrid apps, using native code and all the OS-appropriate design elements.

The hybrid app concept is popular but can have drawbacks as well. Using one codebase for multiple OSes means that developers have to make some compromises. For example, iOS doesn’t have full near-field communications support, and Android and iOS apps have different navigation conventions.

In some cases, with all the extra effort needed to make the “write once, deploy anywhere” concept actually work on multiple platforms, it can be easier to just invest in native app development after all.

Other Considerations

Enterprise mobile apps also need to connect to infrastructure components for push notifications, management and security, analytics, data syncing and connections to enterprise databases and feeds.

Some people say hybrid and Web apps are good enough for enterprise apps. Others say user experience is more important these days, and apps should take advantage of the native features a mobile OS offers. But different apps and situations call for different development approaches and considerations.

 

 

 

Fuente: How to Select App Development Frameworks: Native vs. Web vs. Hybrid – DZone Mobile

Hybrid vs. Native: Choose in 5 minutes! – DZone Mobile

In case you’re befuddled and pondering whether to fabricate a half and half versatile application or a native portable application, don’t stress, this article will help you choose your versatile application procedure in under 5 minutes!

We have discovered curious and confused business visionaries who go insane attempting to settle on the most proficient method to approach which Mobile App is best Native Mobile app development or Hybrid app development. In case you’re befuddled and pondering whether to fabricate a half and half versatile application or a native portable application, don’t stress, this article will help you choose your versatile application procedure in under 5 minutes!

Quick liners on Hybrid Apps and Native Apps before we begin:

  • Hybrid App: Developer increases web code with native SDK. Can be effectively conveyed over numerous stages and is typically the less expensive and quicker arrangement.

  • Native App: This is stage (iOS, Android and so on.) particular and requires one of a kind mastery. However, the maximum capacity of the stage can be utilized which will drive extraordinary client experience and bigger application abilities (particularly around telephone equipment). Can be expensive taking into account prerequisite and take more time to create.

5 Questions to ask before you choose

Do You Need to Utilize Native Components in the Mobile App?

On the off chance that your application is overwhelming on native telephone ability and this is your essential USP, then native application improvement will work best. While building a hybrid app development, contingent upon the system that you receive (there are a few in the business sector), you could possibly have admittance to native components.

How Rapidly Would You Like to Take It to the Business Sector?

An ideal opportunity to market is reliant on different variables like the measure of components and number of assets you have. More assets normally imply that the spending will increment. In the event that you need to dispatch the mobile app development rapidly to the business sector with constrained assets, it is astute to run with half breed application approach, which will dispatch your application on various stages in a brief span.

Do You Have Separate Spending Plans for Designers in Ios and Android (Considering That They Dominate the Market Share)?

In the event that you can dispense separate spending plan for iPhone improvement and advancement assets, and you have freedom of time to take it to the business sector, then you don’t need to stress much; go for native application!

How Frequently Do You Have to Redesign Your Portable Application?

In the event that you have to make incessant overhauls to your application, which implies that the client will need to redesign from the mobile application frequently (and not irritating them with that), then you ought to consider a half and half application. The greatest favorable position for mixture application is that unless you have a basic change of the usefulness in the application, all the substance will be upgraded from web, specifically.

Do you need to have the best client experience?

In the event that you need to make a great Customer experience for Hybrid App Mobile Web, the native application methodology would be better. A cross breed application can never coordinate the level of innovative client encounter that you get in a native application. Notwithstanding, this doesn’t imply that the client experience of a half and half application is terrible.

Conclusion

The response to “Which is better?” is decently nuanced. Native applications offer the best end client experience, yet require the most particular aptitudes and are the most costly to create. Half and half applications have a lower obstruction to passage, are the least expensive to create, and focus on thetop mobile App development companies, yet don’t as a matter, of course, catch the right look and feel of what end clients may expect and for the most part won’t execute too or be as highlight rich. In the event that expense is not an issue, native applications offer the best item, however in more cost-touchy situations, cross breed applications still offer a convincing (if not exactly as great) experience. At last, the answer will go to the organization, engineer, and the end clients as to which arrangement is generally fitting.

The Mobile Zone is brought to you in partnership with Strongloop and IBM.  Visually compose APIs with easy-to-use tooling. Learn how IBM API Connect provides near-universal access to data and services both on-premises and in the cloud.

Fuente: Hybrid vs. Native: Choose in 5 minutes! – DZone Mobile