825331 - Determine what regions are selected for support based on app payment type

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect)

Description

[krupa raj[:krupa]]

steps to reproduce:
1. Select a free app
2. Navigate to 'Compatibility & Payments' page for that app
3. Change the app from free to paid

expected behavior:
a) When the app changes from free to paid, we change the selected regions list likewise to only those regions which will initially support payments.
b) We show a user message to the developer indicating that payments is supported in limited regions.

observed behavior:
Regions selected are not affected by changes to app payment option.

Comment 1

[Wil Clouser [:clouserw]]

David, Maria:  what should we be doing here?

Comment 2

[David Bialer [:dbialer]]

I believe Krupa has captured the expected behavior correctly.  The other thing I notice is that only certain platforms are supported with paid - right now Firefox OS.  While I get a warning message telling me that only Firefox OS apps can be paid, it doesn't let me deselect platforms (or I can't figure out how to do this).  I should be able to changed this (but I digress).


In the case where both conditions are true (the has regions which don't support paid AND the app has platforms that don't support paid), there should probably be a combined message.

The other action that should happen is that its popularity, I assume that is derived from some factor based on the number of installs.  I would think that we should reset 'popularity' - not sure if we should have essentially reset to zero or some other factor?  What you think?

Comment 3

[Wil Clouser [:clouserw]]

(In reply to David Bialer [:dbialer] from comment #2)
> The other action that should happen is that its popularity, I assume that is
> derived from some factor based on the number of installs.  I would think
> that we should reset 'popularity' - not sure if we should have essentially
> reset to zero or some other factor?  What you think?

Historically, popularity is based on usage so resetting it to zero would only change it for ~1 day until all the people using it re-pinged the marketplace.  Flipping from free to paid doesn't change the popularity (read: usage), but I see where you're going.  I'm not sure what the best change would be - perhaps Maria could help.

Comment 4

[Matt Basta [:basta]]

Before I write code for this, I want Maria's input. We have some choices here:

- Disable (gray out) and automatically deselect the regions which don't support payments. This is ideal, but doesn't give the user a feeling of being in control.
- Hide the regions which don't support payments and automatically deselect them. This is the easiest to code for, but has all the disadvantages of the previous option.
- Show the regions which don't support payments (keeping the developer's original region selections) but throw errors until they deselect the regions that don't support payments. This is less than idea because it requires more interaction from the developer, but it ensures they know what's going on.

(the regions in this case are checkboxes)

As soon as I get some input, I'll get this taken care of.

Comment 5

[Maria Sandberg [:mushi]]

Bram knows more about the other dependencies when it comes to submitting an app than I do so I will refer to him to comment on what to do with the regions. 

Regarding the popularity issue: Can we define the use cases when this causes problems? The only thing I can think of is an app "keeping" its sorting rank in a list of search results (ordered by popularity) which could be viewed as a misrepresentation but doesn't seem like a disaster.

If we'd like to change that we need to discuss what we want "popularity" to mean and how it is helping / affecting the user in their actions. Then we can determine how to deal with the popularity rating when an app changes price.

Comment 6

[Bram Pitoyo [:bram]]

Attachment: paid tab - regions and listings

(In reply to Matt Basta [:basta] from comment #4)
> We have some choices here:
> […]
> - Show the regions which don't support payments (keeping the developer's
> original region selections) but throw errors until they deselect the regions
> that don't support payments. This is less than idea because it requires more
> interaction from the developer, but it ensures they know what's going on.

I propose to use this method, but with more info organization to distinguish between regions that currently support payment, and those that don’t support it yet

What we should do is:
* Transfer user’s region choices on the “free” tab over to the “paid” tab
* Reorganize “paid” tab’s region listing
  * Two sections: regions where payment support is available now, and regions where payment is coming
  * It will look different from the region listing found on the “free” tab
* Display a warning message to let user know that:
  * We have transferred his region choice
  * The app is no longer listed in certain region
  * Here are the regions where we cannot sell the app yet
  * When payment support for that region is available, we will automatically make the app listed on that region

By visually separating regions, I think we will be able to communicate our intent without causing a lot of confusion or anger.

Comment 8

[Matt Basta [:basta]]

https://github.com/mozilla/zamboni/commit/88a4a1e39ddb1d2ee14f2630603ad570970ac2ce

Just an update: we are not going to be supporting "Other/New" regions for payments (now or in the future).