Hi Dan -- did you get a chance to write up your findings?
thanks,
-Toby
On Fri, Feb 6, 2015 at 1:46 PM, Tomasz Finc tf...@wikimedia.org wrote:
I'll be eager to see you guys write up your findings after the spikes are
over.
thanks for moving that forward.
--tomasz
On Tue, Feb 3, 2015 at
I'll be eager to see you guys write up your findings after the spikes are over.
thanks for moving that forward.
--tomasz
On Tue, Feb 3, 2015 at 3:05 AM, Gautam Chandna gaut...@opera.com wrote:
OEMs care about the size of their OS, as this is stored in a restricted
read-only area (unless a
Hi, yes app size and yes optimization :-)
App size does matter
OEM's are sensitive to the size of the app for preload. They were satisfied
with our last version that was under 3MB; we'll find out what they will
tolerate. And we will likely push appstore promotion as part of our deep
dive.[1]
sizing == development cost (in man hours)
On Mon, Feb 2, 2015 at 4:04 PM, Dan Garry dga...@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
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 dga...@wikimedia.org wrote:
On 1 February 2015 at 14:48, Toby Negrin tneg...@wikimedia.org wrote:
Dan -- can you please limit the
On 2 February 2015 at 15:39, Carolynne Schloeder cschloe...@wikimedia.org
wrote:
Hi, yes app size and yes optimization :-)
App size does matter
OEM's are sensitive to the size of the app for preload. They were
satisfied with our last version that was under 3MB; we'll find out what
they will
Don't preload apps still get over-the-air updates, often the whole app
re-download?
On Tue, Feb 3, 2015 at 12:39 AM, Carolynne Schloeder
cschloe...@wikimedia.org wrote:
Hi, yes app size and yes optimization :-)
App size does matter
OEM's are sensitive to the size of the app for preload.
Also, can you see what percent of our GS traffic uses 2.3?
I think it will be worth it to get this from actual usage of the app.
Google will report us downloads, but not activations and it is not
infrequent that many users download an app that they do not use at all.
Specially if a mobile web
Dan,
I think this is really important and thank you for highlighting this.
Could you do rough sizing on what it would take to get something like this
out? What if we did this with a pre-load?
Carolynne -- I recommend you start reaching out to Kim as you re-formulate
your W0 strategy.
Lila
On
Creating a separate app to optimize sounds like a good idea. We will check
the market stats on Android versions, and I'll get the scoop from Facebook
on their learning.
I was somewhat surprised that most OEM's we've talked to are shipping
Android 4.x even on low-priced models targeted for
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.
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
I also like the idea, but I think Android is a much better initial target,
as it is much more common in the low bandwidth market from what I gathered.
On Jan 31, 2015 8:52 AM, Brian Gerstle bgers...@wikimedia.org wrote:
Love the idea, and I agree with everything Monte said. We might also need
For sure. Always fun to think about optimising :)
On Jan 31, 2015, at 12:26 AM, Yuri Astrakhan yastrak...@wikimedia.org wrote:
I also like the idea, but I think Android is a much better initial target, as
it is much more common in the low bandwidth market from what I gathered.
On Jan
That sounds like it may be the way to go!
For iOS:
Probably no time for a lite version this quarter, but maybe the current
version could be made lighter?
It could actually be a relatively simple thing to do. In fact, I just did a
quick experiment:
Our current iOS app weighs in at *4.38 MB*.
14 matches
Mail list logo
