Since this is technical, I would say Brian is the best one to talk to.

@Brian it would be good if you could figure out what is the smallest step we can take when first moving to the service. Also keep in mind we will have a requirement to measure and compare the user perceived loading time so we can show that we actually made an improvement. As a start, this can be just be measured by developers (UI testing?) without involving Event Logging.



On Wed, Jun 24, 2015 at 1:03 PM, Bernd Sitzmann <bernd@wikimedia.org> wrote:
If you have any requirements that are missing please let me know. 

Who on the iOS side would be the best contact person to occasionally run things by? 

In particular, right now I'm wondering if the html route is something that iOS devs are comfortable with. Or would you prefer a different route initially, which would be a smaller step for the client, where we still have a JSON payload, similar to what we're using right now, (mobileview, with two requests: lead + rest), but all the DOM transformations already done, unneeded parts of payload removed server-side, plus some data added for gallery in the rest portion?

Thoughts?

Cheers,
Bernd

On Wed, Jun 24, 2015 at 9:07 AM, Corey Floyd <cfloyd@wikimedia.org> wrote:
Thanks again for all the work you put into the docs - really great.

On Mon, Jun 22, 2015 at 2:36 PM, Corey Floyd <cfloyd@wikimedia.org> wrote:
woot!

On Mon, Jun 22, 2015 at 1:17 PM, Bernd Sitzmann <bernd@wikimedia.org> wrote:
We've got a Phabricator project for the Mobile Content Service at https://phabricator.wikimedia.org/tag/mobile_content_service/.


Cheers,
Bernd

_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l




--
Corey Floyd
Software Engineer 
Mobile Apps / iOS 
Wikimedia Foundation



--
Corey Floyd
Software Engineer 
Mobile Apps / iOS 
Wikimedia Foundation




--
Corey Floyd
Software Engineer 
Mobile Apps / iOS 
Wikimedia Foundation