Closed
Bug 821058
Opened 12 years ago
Closed 12 years ago
Add region information to Compatibility & Payments page
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: krupa.mozbugs, Assigned: msandberg)
References
Details
(Keywords: uiwanted, Whiteboard: u=dev c=pmt p=1)
Initially Payments will be enabled for a few select countries. We need a way for developers to know that their paid app will be initially listed in a few countries only. It makes sense to move the region information from Edit Listing page to the Compatibility & Payments page. The region selection should automatically limit to countries which support payments when it comes to paid apps.
Comment 1•12 years ago
|
||
Maria: what is the right thing to do here and what should it look like?
Assignee: nobody → msandberg
Comment 2•12 years ago
|
||
(In reply to krupa raj 82[:krupa] from comment #0) > Initially Payments will be enabled for a few select countries. We need a way > for developers to know that their paid app will be initially listed in a few > countries only. This seems reasonable. > The region selection should automatically limit to countries which support > payments when it comes to paid apps. Why would the developer want to include/exclude regions? If we add more regions later, how do we communicate to existing app devs? I vote to keep this simple and just show a read-only list of supported regions so that the dev is aware. As we support more regions, we can automatically include existing paid apps at a price/currency corresponding to the price tier they have already selected.
Updated•12 years ago
|
Comment 3•12 years ago
|
||
Regions have been moved to the C&P page! https://github.com/mozilla/zamboni/commit/457988441605ba95a1e192847b618de433bd03eb It isn't any different than it was on the Edit Listing page, but we can worry about prettifying it some other time. http://cl.ly/image/3r1f242e0R17
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•