16 votes6 comments · Universal Windows Platform » Dev Center + Store · Flag idea as inappropriate… · Admin →
Side note that the same issue happens with en-us and en (international English), which has bit me a couple times.
238 votes10 comments · Universal Windows Platform » Dev Center + Store · Flag idea as inappropriate… · Admin →
Thanks folks for the suggestion and the on-going commentary. We’re marking this as ‘under review’ to acknowledge that the team is aware of this request. This is a very complicated/hard item for implementation, and there is a general feel that the new accelerated certification process alleviates much of the need (as an update can be published, for most folks, in less than an hour – rather than in 4 days).
That being said, continue to weigh in on the comments section.
A couple questions for those on this suggestion to add clarity.
1 - Is having the ability to only move back one release sufficient? This would mean that a developer could only ever move (n-1) releases back, and that that the Store would not keep any additional 'backups'/'undos'.
2 - And is there an expectation that users could also move downgrade once the developer rolls-back the version (and therefore the phone/Store app would need to support 'down level upgrades'), or that the roll-back would only stop additional users from picking up the 'bad' version of the app?
271 votes45 comments · Universal Windows Platform » Dev Center + Store · Flag idea as inappropriate… · Admin →
Starting this month apps can be transferred from one account to another. To start the process you need to open a support ticket to start the process. Once you submit the request, you’ll get a checklist (for example you need to finish any pending submissions, export the reports). The acquisitions, reviews history and users are transferred, though the historical revenue is not transferred. The feature is available to every app, except if the app has IAP – support for IAP is being investigated for the future.
You can open up a support ticket and ask for an app to be moved today. The app will lose all of the reviews associated with it, but it will be moved between publisher accounts and will retain rank/users.
Which version of Visual Studio are you using? Which OS? And do you have the Windows Phone SDK installed?
Semi-random/clarifying question - if you don't have a Windows Phone, then what kind of app are you building using App Studio?
Another one added after developer conversations this week
Added this after a developer conversation this week
You can also create a screenshot from your device (Windows key + power button)
Edited it for you; great suggestion, btw - thanks for submitting it.
I hope you don't mind, but I updated the title to be more dev-centric and reclassified the suggestion. Please keep the suggestions and votes coming.
FYI - I moved this to the Store forum and tweaked the title a bit
97 votes6 comments · Universal Windows Platform » Dev Center + Store · Flag idea as inappropriate… · Admin →
Thanks for the suggestion. I’m marking this as under review to note that the teams are aware of this suggestion and that it is under consideration.
4,232 votes436 comments · Universal Windows Platform » Device - Phone / Mobile · Flag idea as inappropriate… · Admin →
Currently, the platform provides a number of SMS Access from a system eventing perspective (as of Windows Phone 8.1), and Windows Phone supports sms backup/restore for consumers as part of the base OS (Settings → Backup). What we don’t provide is a backup API.
Using SMS events: Check out the Build 2014 session (http://channel9.msdn.com/Events/Build/2014/2-518) or MSDN docs on background tasks (http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh977056.aspx)
Although the capabilities are there from a consumer perspective (the core ask for the suggestion), I’m marking this as ‘Under Review’ for the API perspective. The team is aware of the ask and it is something that is being considered.
@Mark / @Goncalo - The ability to do backups of apps/sms in 7.x is something that sits pretty squarely in the OS team as a consumer feature (and likely something that is better voiced in http://windowsphone.uservoice.com/ ) - I agree that it would have been great to carry forward my history as I moved from my Lumia 900 to a 920. Your best bet in the short-term is a homebrew solution for backup/restore.
@Juan - The team is looking at how to best mitigate privacy and helping protect the average user. While a declared capability is one route, the team would like to provide a way of having the user better understand what is really going to happen when/if the app is given full control to send/receive SMS on their behalf...which is a pretty powerful privilege...both in terms of having one's life opened up to an anonymous developer as well as a potentially expensive one.
Hi folks - okay, duly noted on the focus of the 'API' aspect of the request. As such, I've updated the status of the request...and moved it back into the 'Under Review' bucket here.
The challenge to this request is how to provide access to the SMS store without compromising the security and privacy of the data in that SMS store. As mentioned in the response, the team provided this capability as a consumer feature only - but I'm curious - what would an SMS backup/restore API provide to the developer community that the WP8 consumer capability to backup/restore SMSs doesn't currently provide (and assume that a net-new API would not come to WP 7.x devices)?
One last item to @andycted - you might be surprised at how opinions can vary. If we're ever at the same event, let's grab a frosty beverage and I can share some very amusing stories. :)
Hi folks, poking my head in here again quite briefly. For folks on the thread on three points:
1. This suggestion (and this site) is around developer APIs; consumer capability to backup SMS in the OS is something that is handled by the OS Platform team - and best discussed over at the consumer UV forums @ http://windowsphone.uservoice.com/
2. As mentioned before, I honestly can't comment one way or another on the importance or status of items on this site until we disclose. As someone who personally changes phones every couple weeks, I can't agree more on a personal level - but I can't comment on the capability on behalf of the product or the engineering teams. I absolutely love your passion and love the fact that your putting your frustration here where engineering can/does see it, but I unfortunately can't do anything to ease or allay it than say 'stay tuned' (for a time period that is also, unfortunately, unspecified :( ).
3. For the ability to create custom keyboards, add your voice/votes to those topics on here on those matters.
@Jason/@andycted - we do keep an eye on things here - frequent commenting is hard without folks reading things into responses and inadvertendtly 'signalling' something that gets WP news pickup (e.g., this happened when I was asking for more details about interest on the native topic on here) - so a group of us silently watch and probe a bit when we think it's necessary.
@andycted - User feedback is an interesting thing. To your point 'it's SO obvious what features a smartphone should have in 2012', there are a couple items here - I agree that probably 80% of the dev capabilities here (and probably about the same on the consumer site) are 'motherhood and apple pie' no brainers, and many of them are items that have already come up in conversations internally and are on our radar. But as well, there are ALWAUS differing opinions in any large company/product - and data always helps in hotly debated topics as folks are fighting over which features stay or get cut...and your voice and your votes help here more often than you could ever imagine. Also, the value, the interesting part, for the spec writers come out from the site in the comments with what folks really want to DO beyond just having them. As well, there still are a surprises in the mix (which I would classify more as 'uncommon' than 'rare'), which is the real delight for our team when we find those wants and needs. :)
Topic of missing features - The phone is a really great product that does many things quite well (and we do have a good showing in the smoked by WP competitions, as you call out). While I do agree that there are definitely features that need to added to further improve the WP experience (particularly for someone such as myself who moves between phones pretty frequently, the SMS point is a sore one for me personally, as well). The team that owns that area is definitely aware of the need (but please still add your voice to the requests - as mentioned earlier, data does help in cutline discussions), and I (as a WP user and customer), as much as you, hope to see a continued improvement in the user experience on the phone.
@Jason - I agree that responses are pretty standardized and not too terribly helpful. While I can (and do) apologize for the general opaqueness of these very generic 'thanks; it's on the list for discussion'...that acknowledgment, along with the promise of 'we are evaluating suggestions and comments' on a semi-weekly basis, is about all we can offer publicly at this time.
When we come up on our next release disclosure, you'll see a large number of changes in the UserVoice forum as we update the site to reflect what's been announced and where we're going...but we can't do much more than 'it's officially under review' until that time. To do so otherwise can not only provide false hope (lots of things get picked up, only to be cut or scope reduced in later milestones - particularly the deeper into a platform you go) or just plain break disclosure/launch plans. There are at least a few other players in the market, and there are many who are concerned with having the more innovative stuff we're working on out there too early.
All of that being said, your thoughts and comments are very much heard. I hope to demonstrate that when we announce the next version, but you'll have to take us on faith up to that point.
Hi folks, a couple quick notes on this. :)
1 - I updated the title of this suggestion to emphasize the API ask in the request (an API to texts for developers); for consumer SMS backup, I would direct folks over to the consumer UserVoice site (http://windowsphone.uservoice.com).
2 - A quick note that Microsoft is looking at all suggestions, and we discuss and evaluate comments in the thread. However, it's important to note that this is a feature suggestion location, and not a place where we will disclose future features or capabilities...those announcements will happen at public events and disclosure points. Once features/capabilities are announced, we will come back here and update the status. As such, please don't take silence as being ignored. Many folks are watching this site and the conversations going on here -- please keep your thoughts and comments coming. :)
708 votes44 comments · Universal Windows Platform » Dev Center + Store · Flag idea as inappropriate… · Admin →
Thanks for the suggestion; I’m marking this as under review for implementation in a future release of the Store.
This topic is a conversation point within teams -- one suggestion that has consistently been given to devs is to consider adding a visual call-out on your Marketplace app icon, marking the app out as having a 'free trial', to encourage folks to take a look at the trial within the paid apps list.