{"id":562,"date":"2017-08-03T10:28:40","date_gmt":"2017-08-03T10:28:40","guid":{"rendered":"https:\/\/www.technosoft.nl\/?p=562"},"modified":"2021-03-16T05:48:01","modified_gmt":"2021-03-16T05:48:01","slug":"nearshoringblogmobile-technology","status":"publish","type":"post","link":"https:\/\/www.technosoft.eu\/nearshoring\/blog\/mobile-technology","title":{"rendered":"Mobile technology"},"content":{"rendered":"

Recently, In-shore and its partners have been discussing this issue, which is always evident in developing mobile applications. In an expert setting, the most widely used techniques and platforms were compared. Not only at the technical level, but also by companies and developers in practice, what the business asks for and what works best.<\/p>\n

Native or Cross Platform?<\/h3>\n

Of course there is the long-standing discussion about native versus cross platform, with more hybrid forms coming up, such as REACT. An unambiguous answer to what is best is not possible, since there are many factors that point to one side or another. Things like speed, reuse of existing code, complexity of back office applications, version management, development efficiency, UI design, available knowledge, API applicability and plug-ins are just a grip from the range of considerations that play a role in choosing the method of development. When mobile development is a strategic choice for your business (and that’s almost always the case these days), a good research for the most appropriate platform is a must. We often see that development is started without a (re) orientation on what is and what is possible.<\/p>\n

Compare development platforms<\/h3>\n

Within our Technology Stack we use Xamarin, Cordova, React native, native iOS (ObjectiveC\/SWIFT) and native Android the most. In order to make a good comparison, these platforms have been reassessed and compared to issues such as applicability, technology and pros and cons. Of course, there are the basic contradictions between native and cross platform upstream, but also the differences based on application in practice. For example support on platform or plug-ins, test capabilities, license fees, exchange with existing development environment, and deployment capabilities.<\/p>\n

 <\/p>\n

The most obvious choice is not always the best. For example, for a healthcare company, we have chosen Cordova development after extensive research, while all development work is done in Microsoft technology, for a multinational in the electronics sector with similar development we have chosen Xamarin and for a company in the parking sector for a mobile web application based on PHP. All based on different grounds, situations, goals and considerations. There is clearly no “one size fits all”<\/p>\n

A few conclusions<\/h3>\n

Although this expert session was the first in a series of sessions, a number of first issues have emerged, which we often encounter in practice.<\/p>\n