You’ve probably seen or read about the move by Facebook to move the Messaging function out of the core application.
I found this from @micmicr the other day and thought it was interesting, but wonder if Deloitte missed some things lurking between the lines. I can’t say I disagree with the findings based on any research or observations, but I do find two things that would benefit from additional research.
1. There is a need for speed. The assumption based on this summary of the research is that Cellular Data or Wifi speeds are slowing down the apps people use. Sure this can be the case especially during peak usage times, but it isn’t the only variable. Poorly written apps, bloated services, large image/video assets among other variable play a role. What this means to me is that there is a perception that users have that apps are perfect and the network is the problem. This is an opportunity for app makers to build apps that are performance minded.
2. People aren’t downloading apps. Well, they are obviously and there are more and more people getting smartphones every day. What they argue, without really saying it, is that 500 apps for reminders, flashlights and pimple poppers are not needed. The app market is starting to mature and kitsch apps are less desirable than quality apps that meet their needs. I do not think this is a bad thing for app makers. I would argue that people are still wanting their favorite brands to be available on their devices. However, they don’t want the website crammed into an app, they want high value, targeted moments that can be expedited by their device.
Great research by the Deloitte team and no doubt more will come as the app space matures. What research do you find interesting?
WebCore layout and JS core
JS benchmark in Jellybean on a Nexus is much faster
event > paint > draw
– for pictures you can represent the whole page without going back to webkit when scrolling or zooming
– software rendering issues though: dependent on the time spent traversing and rasterizing, no 3D CSS, limited support for plugins and video
Honeycomb and beyond
– tile content
– hardware rendering is scroll > draw uses a separate thread for paint to get a new tile
– CSS property to animate HTML elements
– supported on webkit browsers
– On android hardware accelerated and faster than JS
Remainder of presentation is full of code examples and would be better to review the slides. I’ll post a link when it becomes available.