Hi everyone,
On Wednesday, Katherine, Tomasz and I met with Joe Castorena from Google’s Android Play Partnerships team. I’ve split up the most relevant information into a few separate emails, to keep the discussion on each separate point focussed.
Joe informed us of the process for getting featured in Google Play. The long and short of it is that once we decide we’ve got a build that’s worth featuring, we upload it to Google Play and contact Joe. There is a board at Google that makes the decision about whether or not to feature an app and that decision is multifactorial, including factors like what other apps are featured at that time and whether it fits with the current theme of the store (e.g. “Back to School”, etc.). We made need to make some tweaks to get it featured (e.g. he said they might say something like “Make the app more tablet-friendly and we can feature it”), and we’d be informed of what those were.
We’ve got a choice with how we proceed with this:
1. We submit the current form of the production build to be featured. 2. We wait to finish some of the current threads of work (e.g. wrapping up page issues and disambiguation), upload and hold that build unpublished, then submit that to be featured, coordinating the release date with Joe.
I have a mild preference for option 2 as then we can coordinate the release of the new features with the featuring, and get more bang for our buck. That said, I am extremely proud of the app that we have out there right now, so I would be more than happy to submit to be featured if that’s the consensus.
Thoughts?
Dan
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
This is great to hear! As happy as I am with the current state of the app, I would definitely wait to complete some of the features we're currently working on before having it featured (full-text search being highest on the list, and maybe even Nearby?)
-Dmitry
On Fri, Aug 22, 2014 at 6:44 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi everyone,
On Wednesday, Katherine, Tomasz and I met with Joe Castorena from Google’s Android Play Partnerships team. I’ve split up the most relevant information into a few separate emails, to keep the discussion on each separate point focussed.
Joe informed us of the process for getting featured in Google Play. The long and short of it is that once we decide we’ve got a build that’s worth featuring, we upload it to Google Play and contact Joe. There is a board at Google that makes the decision about whether or not to feature an app and that decision is multifactorial, including factors like what other apps are featured at that time and whether it fits with the current theme of the store (e.g. “Back to School”, etc.). We made need to make some tweaks to get it featured (e.g. he said they might say something like “Make the app more tablet-friendly and we can feature it”), and we’d be informed of what those were.
We’ve got a choice with how we proceed with this:
- We submit the current form of the production build to be featured.
- We wait to finish some of the current threads of work (e.g.
wrapping up page issues and disambiguation), upload and hold that build unpublished, then submit that to be featured, coordinating the release date with Joe.
I have a mild preference for option 2 as then we can coordinate the release of the new features with the featuring, and get more bang for our buck. That said, I am extremely proud of the app that we have out there right now, so I would be more than happy to submit to be featured if that’s the consensus.
Thoughts?
Dan
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
That works well with what Bernd said about wanting to submit the app for a UX review first. We can round off these features while waiting for UX review to get back to us, see what we make of the UX review, then submit for featured.
Thoughts on that plan of action?
Dan
On 22 August 2014 18:24, Dmitry Brant dbrant@wikimedia.org wrote:
This is great to hear! As happy as I am with the current state of the app, I would definitely wait to complete some of the features we're currently working on before having it featured (full-text search being highest on the list, and maybe even Nearby?)
-Dmitry
On Fri, Aug 22, 2014 at 6:44 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi everyone,
On Wednesday, Katherine, Tomasz and I met with Joe Castorena from Google’s Android Play Partnerships team. I’ve split up the most relevant information into a few separate emails, to keep the discussion on each separate point focussed.
Joe informed us of the process for getting featured in Google Play. The long and short of it is that once we decide we’ve got a build that’s worth featuring, we upload it to Google Play and contact Joe. There is a board at Google that makes the decision about whether or not to feature an app and that decision is multifactorial, including factors like what other apps are featured at that time and whether it fits with the current theme of the store (e.g. “Back to School”, etc.). We made need to make some tweaks to get it featured (e.g. he said they might say something like “Make the app more tablet-friendly and we can feature it”), and we’d be informed of what those were.
We’ve got a choice with how we proceed with this:
- We submit the current form of the production build to be featured.
- We wait to finish some of the current threads of work (e.g.
wrapping up page issues and disambiguation), upload and hold that build unpublished, then submit that to be featured, coordinating the release date with Joe.
I have a mild preference for option 2 as then we can coordinate the release of the new features with the featuring, and get more bang for our buck. That said, I am extremely proud of the app that we have out there right now, so I would be more than happy to submit to be featured if that’s the consensus.
Thoughts?
Dan
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
That sounds excellent! These are some truly exciting opportunities.
(Regarding having our code featured in tutorials, the code might need a little combing-through, and a little more TLC, but still -- a fantastic idea.)
-Dmitry
On Fri, Aug 22, 2014 at 9:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app for a UX review first. We can round off these features while waiting for UX review to get back to us, see what we make of the UX review, then submit for featured.
Thoughts on that plan of action?
Dan
On 22 August 2014 18:24, Dmitry Brant dbrant@wikimedia.org wrote:
This is great to hear! As happy as I am with the current state of the app, I would definitely wait to complete some of the features we're currently working on before having it featured (full-text search being highest on the list, and maybe even Nearby?)
-Dmitry
On Fri, Aug 22, 2014 at 6:44 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi everyone,
On Wednesday, Katherine, Tomasz and I met with Joe Castorena from Google’s Android Play Partnerships team. I’ve split up the most relevant information into a few separate emails, to keep the discussion on each separate point focussed.
Joe informed us of the process for getting featured in Google Play. The long and short of it is that once we decide we’ve got a build that’s worth featuring, we upload it to Google Play and contact Joe. There is a board at Google that makes the decision about whether or not to feature an app and that decision is multifactorial, including factors like what other apps are featured at that time and whether it fits with the current theme of the store (e.g. “Back to School”, etc.). We made need to make some tweaks to get it featured (e.g. he said they might say something like “Make the app more tablet-friendly and we can feature it”), and we’d be informed of what those were.
We’ve got a choice with how we proceed with this:
- We submit the current form of the production build to be
featured. 2. We wait to finish some of the current threads of work (e.g. wrapping up page issues and disambiguation), upload and hold that build unpublished, then submit that to be featured, coordinating the release date with Joe.
I have a mild preference for option 2 as then we can coordinate the release of the new features with the featuring, and get more bang for our buck. That said, I am extremely proud of the app that we have out there right now, so I would be more than happy to submit to be featured if that’s the consensus.
Thoughts?
Dan
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app for a UX review first. We can round off these features while waiting for UX review to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
Unless there are any objections, I will submit our current production build for UX review on Wednesday 3rd September 2014.
Once that review is complete, we can take a look at their feedback to see how much work is in there, and set a hard deadline. If we finish our work before that hard deadline, cool, we can submit forthwith! If not, then we submit on the hard deadline irrespective of how done we are.
Dan
On 28 August 2014 20:14, Tomasz Finc tfinc@wikimedia.org wrote:
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app for
a
UX review first. We can round off these features while waiting for UX
review
to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
Agreed; I think the current production version should be fine for UX review.
-Dmitry
On Fri, Aug 29, 2014 at 12:00 AM, Dan Garry dgarry@wikimedia.org wrote:
Unless there are any objections, I will submit our current production build for UX review on Wednesday 3rd September 2014.
Once that review is complete, we can take a look at their feedback to see how much work is in there, and set a hard deadline. If we finish our work before that hard deadline, cool, we can submit forthwith! If not, then we submit on the hard deadline irrespective of how done we are.
Dan
On 28 August 2014 20:14, Tomasz Finc tfinc@wikimedia.org wrote:
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app
for a
UX review first. We can round off these features while waiting for UX
review
to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Excellent. I'm eager to hear back from them as one element to guide us forward.
--tomasz
On Fri, Aug 29, 2014 at 6:19 AM, Dmitry Brant dbrant@wikimedia.org wrote:
Agreed; I think the current production version should be fine for UX review.
-Dmitry
On Fri, Aug 29, 2014 at 12:00 AM, Dan Garry dgarry@wikimedia.org wrote:
Unless there are any objections, I will submit our current production build for UX review on Wednesday 3rd September 2014.
Once that review is complete, we can take a look at their feedback to see how much work is in there, and set a hard deadline. If we finish our work before that hard deadline, cool, we can submit forthwith! If not, then we submit on the hard deadline irrespective of how done we are.
Dan
On 28 August 2014 20:14, Tomasz Finc tfinc@wikimedia.org wrote:
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app for a UX review first. We can round off these features while waiting for UX review to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Nobody objected, and it's Wednesday now! I'm going to email our contact at Google Play now and tell him we'd love our current production build to be reviewed.
Dan
On 28 August 2014 21:00, Dan Garry dgarry@wikimedia.org wrote:
Unless there are any objections, I will submit our current production build for UX review on Wednesday 3rd September 2014.
Once that review is complete, we can take a look at their feedback to see how much work is in there, and set a hard deadline. If we finish our work before that hard deadline, cool, we can submit forthwith! If not, then we submit on the hard deadline irrespective of how done we are.
Dan
On 28 August 2014 20:14, Tomasz Finc tfinc@wikimedia.org wrote:
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app
for a
UX review first. We can round off these features while waiting for UX
review
to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Exciting
On Wed, Sep 3, 2014 at 4:16 PM, Dan Garry dgarry@wikimedia.org wrote:
Nobody objected, and it's Wednesday now! I'm going to email our contact at Google Play now and tell him we'd love our current production build to be reviewed.
Dan
On 28 August 2014 21:00, Dan Garry dgarry@wikimedia.org wrote:
Unless there are any objections, I will submit our current production build for UX review on Wednesday 3rd September 2014.
Once that review is complete, we can take a look at their feedback to see how much work is in there, and set a hard deadline. If we finish our work before that hard deadline, cool, we can submit forthwith! If not, then we submit on the hard deadline irrespective of how done we are.
Dan
On 28 August 2014 20:14, Tomasz Finc tfinc@wikimedia.org wrote:
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org wrote:
That works well with what Bernd said about wanting to submit the app for a UX review first. We can round off these features while waiting for UX review to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Quick update, here. We received some feedback from Google Play, and we're working on implementing it all in this sprint. Check out our sprint 40 Trello board https://trello.com/b/fuDbiOqN/mobile-app-sprint-40-android-insert-theme-9-15 if you want more info.
Thanks, Dan
On 3 September 2014 16:26, Tomasz Finc tfinc@wikimedia.org wrote:
Exciting
On Wed, Sep 3, 2014 at 4:16 PM, Dan Garry dgarry@wikimedia.org wrote:
Nobody objected, and it's Wednesday now! I'm going to email our contact
at
Google Play now and tell him we'd love our current production build to be reviewed.
Dan
On 28 August 2014 21:00, Dan Garry dgarry@wikimedia.org wrote:
Unless there are any objections, I will submit our current production build for UX review on Wednesday 3rd September 2014.
Once that review is complete, we can take a look at their feedback to
see
how much work is in there, and set a hard deadline. If we finish our
work
before that hard deadline, cool, we can submit forthwith! If not, then
we
submit on the hard deadline irrespective of how done we are.
Dan
On 28 August 2014 20:14, Tomasz Finc tfinc@wikimedia.org wrote:
On Fri, Aug 22, 2014 at 6:27 PM, Dan Garry dgarry@wikimedia.org
wrote:
That works well with what Bernd said about wanting to submit the app for a UX review first. We can round off these features while waiting for UX review to get back to us, see what we make of the UX review, then submit for featured.
Do we have a date to make this happen? Let's keep the wheels moving.
--tomasz
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Dan Garry, 15/09/2014 22:28:
Quick update, here. We received some feedback from Google Play,
Nice.
and we're working on implementing it all in this sprint. Check out our sprint 40 Trello board https://trello.com/b/fuDbiOqN/mobile-app-sprint-40-android-insert-theme-9-15 if you want more info.
Couldn't find anything there, unless it's https://trello.com/c/DpHf0vu0/4-1-add-xxxhdpi-launcher-icon
Nemo
It's all of these, as well:
https://trello.com/c/5WejUXDj/1-5-rewrite-page-browsing-activity-as-fragment... https://trello.com/c/l2ouTvnf/2-5-make-every-other-activity-launched-from-na... https://trello.com/c/OOtykxBl/3-5-make-the-search-bar-into-an-actual-actionb...
On Thu, Sep 18, 2014 at 10:34 AM, Federico Leva (Nemo) nemowiki@gmail.com wrote:
Dan Garry, 15/09/2014 22:28:
Quick update, here. We received some feedback from Google Play,
Nice.
and we're working on implementing it all in this sprint. Check out our sprint 40 Trello board <
https://trello.com/b/fuDbiOqN/mobile-app-sprint-40-android-insert-theme-9-15
if you want more info.
Couldn't find anything there, unless it's https://trello.com/c/DpHf0vu0/4-1-add-xxxhdpi-launcher-icon
Nemo
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
That's so great! :)
On Aug 22, 2014, at 3:44 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi everyone,
On Wednesday, Katherine, Tomasz and I met with Joe Castorena from Google’s Android Play Partnerships team. I’ve split up the most relevant information into a few separate emails, to keep the discussion on each separate point focussed.
Joe informed us of the process for getting featured in Google Play. The long and short of it is that once we decide we’ve got a build that’s worth featuring, we upload it to Google Play and contact Joe. There is a board at Google that makes the decision about whether or not to feature an app and that decision is multifactorial, including factors like what other apps are featured at that time and whether it fits with the current theme of the store (e.g. “Back to School”, etc.). We made need to make some tweaks to get it featured (e.g. he said they might say something like “Make the app more tablet-friendly and we can feature it”), and we’d be informed of what those were.
We’ve got a choice with how we proceed with this: We submit the current form of the production build to be featured. We wait to finish some of the current threads of work (e.g. wrapping up page issues and disambiguation), upload and hold that build unpublished, then submit that to be featured, coordinating the release date with Joe. I have a mild preference for option 2 as then we can coordinate the release of the new features with the featuring, and get more bang for our buck. That said, I am extremely proud of the app that we have out there right now, so I would be more than happy to submit to be featured if that’s the consensus.
Thoughts?
Dan
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation _______________________________________________ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
The time commitment (any participation for heuristic evaluation) expected from us but it sounds like a great platform for reach, we should do it. Usually their feedback is about improving existing stuff and not adding new features. Having lead images and the disambig/ page issues in the build we submit to them would be super useful.
---- Vibha Bamba Senior Designer | WMF Design
On Sat, Aug 23, 2014 at 10:08 AM, Monte Hurd mhurd@wikimedia.org wrote:
That's so great! :)
On Aug 22, 2014, at 3:44 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi everyone,
On Wednesday, Katherine, Tomasz and I met with Joe Castorena from Google’s Android Play Partnerships team. I’ve split up the most relevant information into a few separate emails, to keep the discussion on each separate point focussed.
Joe informed us of the process for getting featured in Google Play. The long and short of it is that once we decide we’ve got a build that’s worth featuring, we upload it to Google Play and contact Joe. There is a board at Google that makes the decision about whether or not to feature an app and that decision is multifactorial, including factors like what other apps are featured at that time and whether it fits with the current theme of the store (e.g. “Back to School”, etc.). We made need to make some tweaks to get it featured (e.g. he said they might say something like “Make the app more tablet-friendly and we can feature it”), and we’d be informed of what those were.
We’ve got a choice with how we proceed with this:
- We submit the current form of the production build to be featured.
- We wait to finish some of the current threads of work (e.g.
wrapping up page issues and disambiguation), upload and hold that build unpublished, then submit that to be featured, coordinating the release date with Joe.
I have a mild preference for option 2 as then we can coordinate the release of the new features with the featuring, and get more bang for our buck. That said, I am extremely proud of the app that we have out there right now, so I would be more than happy to submit to be featured if that’s the consensus.
Thoughts?
Dan
-- Dan Garry Associate Product Manager, Mobile Apps Wikimedia Foundation
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l