By Adam Nagy
My colleague and I attended this event last week. It was quite busy, full of various companies exhibiting.
Their services ranged from app monitoring, building and testing software to full app design and delivery. List of attendees: http://www.apps-world.net/europe/exhibitions/exhibitors
On the way in we ran into an ADN member as well, http://www.linknode.co.uk/
There were many lectures and panels from which the most interesting topic to me that kept coming up was HTML5 vs native apps. I drew the following conclusions from the discussions about HTML5 (some of which I already knew):
- implementing a cross platform HTML5 solution can be just as expensive as creating multiple native apps
- lots of available components create confusion about which ones to use
- very few people are really good at JS
- java is completely different from JS
- JS is a third class citizen on some devices
- big apps are written in other languages
- it's the UI you will be fighting with
- try to keep most code on server side
- if you want to use JS but also need native functionality, then use solutions like PhoneGap
- some companies do prototyping in HTML5, but the final app will be native
- use HTML5 if developers already know JS - e.g. in case of a web development team
Another interesting thing was AppMachine, which can be used to create an app by putting various components together like a LEGO structure. Depending on how successful this product becomes it could be interesting for companies to provide their own building blocks as well to make it easier for 3rd parties to consume their services.
Subscribe
Comments