Before you begin coding a mobile application, there are several questions you need to answer.
● How many platforms am I going to support?
● Do I want to support a web app?
● Which platform should I start with?
And the question we are going to look at in this blog post…
● Should I code natively or use a cross-platform method?
First, let me give a quick definition of the two options.
Native: This means you code for each platform. Meaning, you use XCode for iOS development, Android Studio for Android development, and so on.
Cross-Platform: “Code once, run everywhere.” Write your code once, usually with HTML5/JavaScript, and run the application on multiple platforms.
Now, let’s look at the question again: Should I code natively or use a cross-platform method?
After reading the definitions, it may seem obvious that you would want to choose cross-platform because it only requires you to code your application once. But there’s another piece of information missing that you will need to make your decision. When you code cross-platform, there’s a chance you will miss some native functionality. For example, the overall look and feel of your application may not match the platform it is running on. Or, you may not be able to access all the features on say an iPhone camera or any other feature that is platform specific.
With all of this in mind, the real answer to the question is: It depends. I know, that’s not the straightforward answer you were hoping for. But it is the correct answer. The way you code your mobile application depends on the way you want your application to be used. If you want to be able to access all of the platform specific features (or even just a few key ones), it is probably worth it to code natively. Or, if you want your application to have the look and feel of the platform it is running on, it is probably worth it to code natively. If the overall look and feel and platform specific features aren’t as important to you, you may want to look into some cross-platform solutions such as Appcelerator, but there are many solutions and it’s important that you find the right one for you.
If you decide to go with cross-platform development, check out my next blog on cross-platform CMS builders.
Soft Skills for Tech Leads: How They’ll Help You Excel at Your Role
If you manage a team, you already know that this experience can be as challenging as it is rewarding. At Sparq we have different management roles and one of the most essential is the Tech Lead position. In addition to being seasoned developers, Teach Leads need to be able to mentor up and coming talent. One of the ways they do that is by utilizing soft skills. In this article, Delivery Lead Rodrigo Trelles explores the most important soft skills to be a successful Tech Lead.
Exploring the World of a Site Reliability Engineer (SRE)
Technology is advancing rapidly and the new advances introduce new roles and responsibilities. Among the most significant roles is the Site Reliability Engineer (SRE). This article will explore the role of an SRE, how it differs from a software developer and the essential skills required to succeed in the field.
Automated Testing Applied: How This Practice Can Help Developers Across Projects
In this article, Technical Lead Pablo Carballo shares how automated testing practices have made his team's work more efficient and diverse.
Inside the Minds of Digital Innovators: Highlights from OctoTalks Podcast
Creating exceptional digital experiences involves a blend of creativity, strategy and technology. Octobot, a company that was recently acquired by Sparq, hosted a podcast that delves into these elements by showcasing the visionaries who dream up and build these experiences. In this blog post, we want to share some highlights about the conversations and invite you to give it a listen!