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(a)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(a)wikimedia.org> wrote:
woot!
On Mon, Jun 22, 2015 at 1:17 PM, Bernd Sitzmann <bernd(a)wikimedia.org>
wrote:
We've got a Phabricator project for the
Mobile Content Service at
https://phabricator.wikimedia.org/tag/mobile_content_service/.
Reminder: docs are at
https://www.mediawiki.org/wiki/RESTBase_services_for_apps
Cheers,
Bernd
_______________________________________________
Mobile-l mailing list
Mobile-l(a)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