Yes, moving transformations that currently the client does to the server is one of the approaches the service is doing. Well, it's doing some already but hopefully more soon.
And now for another service announcement:
Following this discussion, during our prioritization meeting earlier we had a discussion about the missing role of a tech-product guy. (Was is tech-pro or pro-tech? I don't remember.) In any case it'll be more technical than a traditional PO role, or even the aforementioned tech-pro/pro-tech. To keep a long story from getting longer, I've volunteered to play that role for the near-term future.
Side note: What this also means for the Android team, is that I'll have less time coding on the Android app, and split my time mostly between Mobile apps Node.js service lead and Android tech lead roles.
I'm going to reach out more in the upcoming week(s) to figure out a few things:
* Collect near-term requirements + add Phabricator tasks.
* Prioritize them.
* Reach out to the web team to learn what this team's plan is for their Node.js service and see if/how much we can share between apps and web.
-Bernd