Facebook Moves Messaging

You’ve probably seen or read about the move by Facebook to move the Messaging function out of the core application. 

Why is this important? 
The rationale shared by ReadWrite suggests that the the experience is not ideal for users. In TechCrunch, the quote from Zuckerberg goes on to say that messaging was “second-class” causing more “friction” and they want to provide a “more focused experience” for messaging through the Facebook platform.
 
I would suggest that this move is a good ammunition for clients that want to cram their entire digital experience into a single mobile application. It is a practical demonstration that Facebook recognizes that, to quote Michael Griffitha focused and guided experience is the best way to extend their brand and meet the needs of their users. 
 
Does this mean every app by every client should have multiple applications? Obviously the answer is no, but you can also look at this as an opportunity to guide the core experience the client is trying to provide for their customers. Are they focused on the right thing? Are they asking for features/functionality “because”? Are they deriving their decisions with data to back the assumptions? Do they want to be a Jack of all trades and master of none? Do they understand the risks and rewards that go with the complexity of one app to do everything?
 
Reference:
Advertisements

Link

Deloitte Survey

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?

Android WebView

Android WebView
Nicolas Roard

Architecture WebKit
WebCore layout and JS core

JS benchmark in Jellybean on a Nexus is much faster

Reder loop
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 Animations
– 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.