sizing == development cost (in man hours)

On Mon, Feb 2, 2015 at 4:04 PM, Dan Garry <dgarry@wikimedia.org> wrote:
I've scheduled 30 minutes on Wednesday for myself and the tech leads (Adam, Dmitry) to scope out a Wikipedia Lite app.

Dan

On 2 February 2015 at 13:59, Dan Garry <dgarry@wikimedia.org> wrote:
On 1 February 2015 at 14:48, Toby Negrin <tnegrin@wikimedia.org> wrote:
Dan -- can you please limit the scope to sizing the android app? I think that's more relevant to reaching people in the developing world.

I think that depends. In a world where we're focussing on preloads, the size of the app is pretty immaterial as the user isn't paying the cost for downloading it. In that world, the best optimisations to make are probably reducing network traffic and improving performance on slower devices, things where there's lot of room for improvement in our code base. Also, our Android app is also an order of magnitude smaller than Facebook's Android app, so that's less of an issue for us. Facebook evidently decided to TACKLE ALL THE THINGS with Facebook Lite.

Also, can you see what percent of our GS traffic uses 2.3? Google has it at about 10% globally but we need to understand our target market better. You might also want to check in with your new contact at App Annie to see if they have useful GS data.

Absolutely.

Dan

--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation



--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation