android studio development pros and cons

I believe that before entering the world of cross-platform development of mobile apps we need to elaborate more on native apps. In this article I'd like to focus on mobile development, analyze the advantages and disadvantages of cross-platform approach and answer the question: 'Is it worth it to reject classic approach in favor of cross-platform one'?Īs it was mentioned in the introduction, mobile apps can be separated into two categories: classic (we will call them 'native' later on) and cross-platform.

Different frameworks for the cross-platform development handle this problem differently: some compile the code to a native one for a specific platform, others use middlewares between a platform and a cross-platform code, but the principle stays the same: you write the code once and it is ready to be used on several platforms. This approach, compared to the classic native one, lets the developer use one codebase for different platforms, eliminating the support of different versions of one app. At this point we have to go back to our question about cross-platform approach.

The result of that is interesting: several applications, created using different technologies and programming languages, look and function the same. Several development teams (each for each platform) make apps using native tools they regularly organise meet-ups to make sure that the apps on different platforms are identical in design and functionality so that the user who changed the platform may continue using the app without experiencing any difficulties.

Android studio development pros and cons