I\u2019m a huge proponent of hybrid mobile app development. I work on the Ionic team at OutSystems, I create content around Ionic\u2019s tools and services, and I\u2019m even writing this for the Ionic blog so it\u2019s completely fair to say I have a bias (as well as a vested interest) in the success of Ionic. We create elegant solutions that solve the problems developers face and I take pride in sharing those solutions because I believe it makes development easier.
Today, I want to take a different approach. As someone who has defined strategy for mobile app development projects I want to remove my Ionic cap and take a holistic look at the hybrid versus traditional mobile app development debate in a way that doesn\u2019t focus on what Ionic has created. During my time working on mobile app strategy I found myself directly contributing to native and hybrid codebases so I can speak to the challenges associated with multi-platform development without needing to focus on specific technologies. My goal is to analyze the conversation to help you choose what\u2019s best for your project and get you on a path that helps make your projects successful. Whether that includes Ionic or not!<\/p>\n\n\n\n
First, there are a ton of caveats to mobile app development strategy but in my experience there are likely three main categories that development teams look at when choosing a technology: Time, money, and resources. While there are development teams that don\u2019t have to take these categories into consideration, every mobile app development project I have worked on has been constrained in one way or another by one of these categories. Given my experience with mobile app development I am making the assumption that you and your teams are likely constrained by these categories.<\/p>\n\n\n\n
Second, there\u2019s a lot of fanaticism in app development especially when defining which technology or approach is \u201cbetter\u201d. If I have learned anything in the last ten years of app development it\u2019s that \u201cbetter\u201d is relative to the boundaries of your project. In the words of Adam Savage, \u201cEvery tool\u2019s a hammer\u201d so you can really make your mobile apps with a lot of different technologies but I would rather put nails in a wall with an actual hammer instead of my MacBook Pro. My point is that I want to help you frame the scope of your project to narrow down<\/em> the list of tools instead of just handing you an irrelevant tool. My aim isn\u2019t to overcome the fanaticism of certain tools or technologies so I\u2019m making an assumption that you are defining strategy agnostically<\/em>. Of course, if your team is technology locked then do what\u2019s best for you and your team with the tools available to you.<\/p>\n\n\n\n With that being said, let\u2019s dive into it!<\/p>\n\n\n\n According to a recent article from Ionic, \u201cthere are more than 5.5 million Android and iOS mobile apps on the market.<\/a>\u201d This means that developers and development teams are required to produce high-quality applications to not only meet industry standards for an ever-evolving regulatory landscape but also exceed user expectations defined by an ecosystem shaped by much larger development teams. Mobile apps are getting more difficult to build in order to stay compliant but you and your teams are competing against much larger development teams to get users in your mobile apps. The reality is that creating compliant mobile apps with killer user experiences can take a significant amount of time, money, and resources and those larger development teams likely have what they need to do that. <\/p>\n\n\n\n However, creating high-quality mobile apps that exceed user expectations while staying on budget and meeting deadlines is difficult even with well-equipped development teams. There are challenges creating mobile apps with any approach that you and your teams use. Fortunately, there are ways to streamline the software development processes and produce superior mobile apps but it requires us to look at what strategies are available to us.<\/p>\n\n\n\n When discussing mobile app development there are typically two main styles of application development strategies that people refer to: Traditional & Hybrid app development.<\/p>\n\n\n\n Traditional mobile apps, or native apps, are written in a language and format specific to their platforms. In this case it would refer to Swift\/SwiftUI\/UIKit for iOS in Apple\u2019s ecosystem and Java\/Kotlin for Android in Google\u2019s ecosystem. These traditional mobile app development ecosystems use different languages as well as approaches to build apps, test apps, deploy apps, and require specific expertise depending on if you\u2019re building mobile apps for iOS or Android.<\/p>\n\n\n\n Hybrid mobile apps are written in a single codebase and installed directly on the user\u2019s device. While you still need to work with the nuances in iOS and Android when it comes to testing, deploying, and managing the apps the complexity gets drastically reduced by having a single codebase. You don\u2019t need to have specialized talent working individually on an iOS or Android app in parallel to deliver for both platforms and every developer on your team can contribute to both platforms. This is accomplished by wrapping the underlying code in a native container that runs on the user\u2019s device.<\/p>\n\n\n\n Fundamentally, traditional and hybrid applications rely on three layers of architecture: The data layer, the business layer, and the presentation layer. While the debate of traditional and hybrid app development strategies typically focuses on the presentation layer it\u2019s important to understand that every part of the architecture contributes to determining the strategy of what will be chosen for the presentation layer. The data and business layers each consume their own time, money, and resources so limitations can have a significant impact on what can be done with the presentation layer. For instance: if you have a limited number of full-stack developers whose talents all rely on JavaScript, and they utilize JavaScript throughout the architecture of the application, then it\u2019s more likely that the team will try to utilize that skillset in the presentation layer to reduce complexity when building the app. Teams can definitely go against this but the time, money, and resources required to build the app can grow dramatically.<\/p>\n\n\n\n As someone who has contributed to native codebases, there are benefits to choosing traditional development when you are building your mobile apps. The benefits include the ability to use the latest \u2013 and greatest \u2013 features of the platform you are developing for, the ability to have more polished user experiences, and the chance at having the \u201cmost performant\u201d app. It might seem contradictory to discuss these benefits of traditional mobile app development on the Ionic blog but I do think there is a time and place for traditional app development.<\/p>\n\n\n\n In my opinion, I believe the greatest advantage to traditional mobile app development is the ability to utilize the newest or platform specific features developed by Apple and Google for their ecosystems. The reason this is an advantage is because hybrid platforms tend to lag with native integrations for these features (requiring you to develop the integrations yourself) or it\u2019s just not practical because the feature you are developing wouldn\u2019t benefit from a hybrid development approach. A perfect example of this can be found in a recent article<\/a> I wrote on using AR Quick Look with Capacitor where I leveraged Apple\u2019s AR technologies in a hybrid app. You can do it but, outside specific use cases outlined in the article, it doesn\u2019t make sense to integrate it into most projects since that feature only exists in Apple\u2019s ecosystem and it would just be easier to develop it there.<\/p>\n\n\n\n The next advantage is polished user experiences. Apple and Google both have their own user interface guidelines for building successful apps within their ecosystems that vary from one another. Users in those ecosystems expect their mobile apps to look and function in specific ways so, in a hybrid approach, you might be making some level of sacrifice for cross-platform capabilities that you wouldn\u2019t have to take in a native development approach. You also have the ability to fine-tune in greater detail each platform\u2019s user interfaces and user experiences than what is available using a hybrid development approach.<\/p>\n\n\n\n The last benefit is performance. The reality is that with a hybrid approach you are adding a layer and there is a cost in performance that happens that wouldn\u2019t necessarily exist with a traditional mobile development approach. This is especially true with Apple\u2019s ecosystem where the code is literally developed for the hardware that it\u2019s running on. This means that with native codebases you can technically<\/em> create \u201cmore performant\u201d apps than what you can utilizing a hybrid approach.<\/p>\n\n\n\n While these benefits look<\/em> good on paper, practically, it\u2019s not beneficial when developing your applications in most cases. Few projects utilize the newest features within the first several months of release and, by the time development teams do plan on integrating those features, they are usually available for use in hybrid development approaches or the features wouldn\u2019t be beneficial on multiple platforms (i.e. the AR Quick Look project I mentioned earlier). In the case of fine-tuned user experiences, the experiences become overly engineered to the point that you lose cohesiveness between the different versions of your mobile apps and they turn into completely separate applications making it increasingly difficult to manage. Then performance, if you read my article<\/a> on performance, is a diminishing return that is drastically dependent on the actual architecture of your apps and has minimal impact when directly compared.<\/p>\n\n\n\n These challenges aren\u2019t the only ones associated with traditional development. Code reusability is a fairly significant challenge especially when speaking of any of the potential benefits that I outlined above. A development team can use the latest features released by Apple or Google but, in order to have both versions of the mobile app utilize those features in a traditional app development approach, it has to be developed twice and usually in different ways (i.e. this issue<\/a> I encountered with a video streaming app\u2019s protocols). Another challenge is security as both platforms require individual security implementation and rigorous testing to ensure that your apps are secure.<\/p>\n\n\n\n This isn\u2019t to say that a traditional mobile app development strategy is a flawed approach, there are benefits as I outlined above, but I think it\u2019s important to understand that the time, money, and resources necessary to see those benefits realized is a high bar to reach for most teams. Unless your organization is all-in financially and ready to have dedicated iOS and Android developers<\/em> your teams are likely to hit a wall before those benefits are realized.<\/p>\n\n\n\n As someone who has also contributed to hybrid codebases, there are benefits to choosing this strategy for building mobile apps as well. The benefits for this strategy include code reusability, the ability to leverage existing web development talent, and the ability to include a significant amount of native features. While not all hybrid development tools have these benefits, and it\u2019s important to research which tools do, the tools that Ionic offers do have these benefits.<\/p>\n\n\n\n The greatest benefit of hybrid mobile app development strategies is the ability to reuse code. In a hybrid development approach a development team can develop their project in a language like JavaScript then deploy the project to iOS and Android utilizing just that single codebase. Not only does that ensure that developers don\u2019t have to create a separate iOS or Android codebase (saving time, money, and resources during development while getting to market faster) but they can also manage both versions of the code from that single codebase. The other significant advantage is that some hybrid development frameworks like Capacitor actually offer more than just the ability to deploy to iOS and Android but also the web and desktop.<\/p>\n\n\n\n The next benefit is the ability to leverage existing talent. In my experience, development teams don\u2019t typically have the resources for dedicated iOS and Android developers or the team composition to support that type of development. This means that mobile app development projects usually end up getting supported by web development teams that then have to try to learn the required skills to build mobile apps. Not only is this incredibly time consuming but it puts a significant strain on developers when they are already juggling a fairly substantial workload. In the case of hybrid app development, web developers can use their existing skills to build mobile apps significantly reducing the challenges associated with learning new languages. Further reducing the time, money, and resources needed to start new mobile app development projects.<\/p>\n\n\n\n Another benefit of utilizing a hybrid mobile app development strategy is ability to leverage native features cross-platform. While this somewhat plays into code reusability, the ability to communicate with device-level features (i.e. camera, push notifications, etc.) on iOS and Android via simple plugins makes hybrid mobile app development strategies incredibly powerful especially when a significant amount of device-level features are supported. It demonstrates that you don\u2019t need to employ a traditional mobile app development strategy to deliver fully functional mobile apps for the vast majority of use cases. Sure, there are some outliers like what I mentioned when talking about traditional app development strategy but most projects are covered by what is already available. If there is a plugin that\u2019s missing then there are solutions that allow you to create your own plugins.<\/p>\n\n\n\n There\u2019s a lot of benefits to utilizing a hybrid mobile app development strategy but there are challenges as well. While I outlined a good portion of the challenges when discussing traditional mobile app development there is a challenge that I didn\u2019t discuss: You still need some functional knowledge of working within Apple\u2019s and Google\u2019s mobile app ecosystems. While you have a singular codebase that code still needs to be deployed to the individual app stores and they both have their own processes for testing and deployment. There are tools to help make this process easier but your team will still need some level of native app deployment knowledge that they might not otherwise know.<\/p>\n\n\n\n While choosing a strategy is dependent upon the boundaries of your project there are a few factors I have learned that can help you narrow down your strategy. These factors include team composition, the requirements of your project, costs, ongoing maintenance, and the future state of your project. Luckily, these can be answered by asking yourself a few simple questions:<\/p>\n\n\n\n If you answered \u201cno\u201d to the majority of these questions then you would likely benefit from utilizing a hybrid mobile app development strategy for your project or at least it\u2019s worth plotting out what that path would look like for your team. If you answered \u201cyes\u201d to the majority of the questions then you might be better suited to the traditional strategy.<\/p>\n\n\n\n There\u2019s caveats to these questions but, if you’re still skeptical or want to understand more about how those factors help define strategy, be sure to check out my in-depth talk<\/a> where I go into further details on factors and strategy.<\/p>\n\n\n\n Determining whether to utilize a traditional or hybrid mobile app development can be a daunting task but, by understanding the different benefits and challenges, it can help make the decision easier. By taking the fanaticism out of the decision and thinking about the different strategies as tools to help you accomplish your app development project it\u2019s much more effective to narrow down a strategy for your use case. Of course if you have any questions about strategy or how our tools can help you with your strategy then be sure to check out our YouTube channel<\/a>, blog<\/a>, discord<\/a>, or reach out to us directly<\/a> and we\u2019ll be more than happy to steer you in the right direction!<\/p>\n","protected":false},"excerpt":{"rendered":" I\u2019m a huge proponent of hybrid mobile app development. I work on the Ionic team at OutSystems, I create content around Ionic\u2019s tools and services, and I\u2019m even writing this for the Ionic blog so it\u2019s completely fair to say I have a bias (as well as a vested interest) in the success of Ionic. […]<\/p>\n","protected":false},"author":103,"featured_media":6216,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"publish_to_discourse":"","publish_post_category":"","wpdc_auto_publish_overridden":"","wpdc_topic_tags":"","wpdc_pin_topic":"","wpdc_pin_until":"","discourse_post_id":"","discourse_permalink":"","wpdc_publishing_response":"","wpdc_publishing_error":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1,164],"tags":[151,144,3,286,287],"class_list":["post-6214","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-all","category-business","tag-capacitor","tag-hybrid-app-development","tag-ionic","tag-strategy","tag-tradtional-app-development"],"acf":[],"yoast_head":"\nBackground<\/h2>\n\n\n\n
Strategies<\/h2>\n\n\n\n
The Benefits and Challenges Of Traditional Development<\/h2>\n\n\n\n
The Benefits and Challenges of Hybrid Development <\/h2>\n\n\n\n
Determining A Solution<\/h2>\n\n\n\n
\n
Final Thoughts<\/h2>\n\n\n\n