Devlopment tales

When looking at the existing JavaScript solutions for building native iOS and Android apps, it's a fact that they're powerful and can extremely reduce the amount of application development time. On the other side it's also clear that they come with drawbacks and limitations. It depends heavily on a project's requirements and of course on the developer skills and sensibilities. App performance and UI responsiveness are the main aspects when it comes to the question of using a JavaScript solution or not (native apps with a single C# code base can be realized with Xamarin). It should be clear that WebView wrapper approaches will never reach native-quality UI performance. So developers should start with a proof of concept when choosing a HTML-based WebView solution: mastering dynamic data and optimizing form controls are non-trivial tasks. The Mobile App Framework Matrix represents a comparison and documentation of current technologies for building native iOS and A...

Google  I/O developer conference 2015 unveiled new version Android M. It looks very promising. As told, there are now over 4,000 apps for Android Wear and designers have created more than 1,500 watch faces.  There is deeper integration of Google Now into Android. So, Google Now cards will be able to appear everywhere in the phone, ready to be called up within apps or the Web via a feature Google calls "Now on Tap". Will get quick answers to quick ques. Eg: card on a movie/event while sending email.  With M, the app will download and install without presenting permissions required, but then ask for those permissions at the time it is first looking to take action. Android Studio Ide is the tool everyone should use for app development. On testing end, Google is adding a feature into its tools that lets developers run automated tests of their Android code against 20 popular devices at no charge. It builds on last year’s acquisition of Appurify. Android devel...