Over the past two years, we have done some pretty exciting work in custom android builds. As a part of our learnings, we collated the core concepts that we have drilled down to get the expertise. We will be sharing these in a series of blog posts in details. Here is a glimpse of the topics we will cover.

When we started exploring Flutter for cross-platform app development about four months ago, we wanted to explore all the features that Flutter offers. We came up with our own analysis of what works properly and what needs a bit more work. Apart from the obvious advantages that Flutter offers that we’ve mentioned in our earlier blog post, we divided our efforts into three categories:

Often in times, during the development of an iOS or Mac based application, developers come across situations where the app needs to interact in some way with a webpage that is being loaded. This is not equivalent to loading a REST API but actual loading of a web page within the application. Though there have been other components within iOS (UIWebview) and Mac (WebView) separately in the past,

Flutter is the new and upcoming cross platform mobile application development platform built and supported by Google. With the increasing number of cross-platform solutions in the market like Xamarin, React Native and now Flutter, we, at Innominds, have updated our skills for our internal proof of concepts (POCs) and advocating them to our customers, as and when required.

With the abrupt increase in the development methodologies for mobile app development, it has become challenging to choose the right method to develop an application. The current market has plenty of frameworks, technologies, and approaches with a varied number of languages to work and complete that niche mobile app idea.