ezoehunt
commented
10 years ago We're archiving prior work and will update this repo shortly with the team's current thinking.
Closed tsmuse closed 10 years ago
ezoehunt
commented
10 years ago We're archiving prior work and will update this repo shortly with the team's current thinking.
Notes from today's meeting
Concerns re: screens/platforms - will discuss. The latest discussion was to remove platforms altogether. We should pursue that.
Consider manifest before screens/platforms - so user can get feedback quickly on manifest
Screenshots - complex - figure this out - how to get developers to add the right screensizes per screen size - make a Github issue and user story. Consider a checklist.
needs flash checkbox - is there any reason why we need to ask this? Can we somehow auto-reject this at manifest sub time?
Creating a payment account - just a heads up, creating a Bango payment account and a Boku payment account is very different. With Bango we have an api and can show you a form to fill out your details. For Boku we need to have you view docs on MDN before we take you to the Boku portal (https://bugzilla.mozilla.org/show_bug.cgi?id=989513#c19).
Need an easy way to view a payment account when assigning a payment account to a specific app. Might need a quick link rather than relying on top nav.
Would be good to understand what countries are available before I commit to "all countries."
Let's de-emphasize hosted apps. They aren't where we need to be right now. We've agree package is the default.
"Responsive" is not needed. Agree remove it.
Total steps to upload an app appears to be 10-12 with new flow. We should be reducing this number, not increasing it. (ie team members step seems superfluous). We're gonna test this.
No mobile interface to edit details? Are we doing mobile first for editing here? +1 I would like to be able to view my listing (esp stats!) and maybe do some editing on mobile
Explore making parts of the dev hub mobile friendly
Tooltips are a cool idea (got those in the style guide)
Screenshots per form factor? How to do this?
Category logos are great
Save/submit is confusing (I know you said you'd clarify)
Availability/pricing: "email me when new countries appear" - I don't think this is going to work. We don't want to require people to come back and opt in to new countries. Or am I misunderstanding that this is?+1 allow people to get auto-signed up new countries and get notified when new country is added. Fix the confusion.
Where is the request/requirement for carrier filtering coming from? We don't support that and have actively opposed it up until now. Kill it.
The example showed tracking specific in-app purchases. I think we've been actively avoiding that also because it's a lot of management overhead for a developer (and it also seems to lock them in to our payments system). Is this being requested by someone?
Note to fix 3 pricing options - free vs paid then choose in-app purchases.
Once serverless in-app payments land, is this a requirement? (a question for kumar)
Only showing relevant payment accounts for the regions I chose is a good idea +1 +1
In the example there are different CC prices based on different platforms. I'm confused why this would ever happen
Have a brain-stormey meeting around this idea and platform selection
How does price per region scale? The example groups some european countries and some latin american countries and looks decent but who is making those groups and maintaining them? Do testing around how countries are grouped.
May need to redesign payment/price selector UI part of the flow due to features being dropped from the road map