MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[Ratings and Reviews Prompt] Author-submitted vs. crawled store information
@diekus is already working on this.
Since Dec 3, 2020.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
There is a difference between indie app stores where anyone can submit apps to and that are crawl-based (they crawl regularly and update the local information they have about an app like, for example, automatically created screenshots) vs. submission-based app stores that have the requirement that the submitter be the verified author and submitter of all screenshots. While the former kind of app stores may recreate their local info on a regular basis, the latter may be stuck with the initial version.
Assuming the case that a news app is listed on an app store of the former and the latter kind, the screenshots in the store listings may be different on both stores. A review that, for whatever reason, makes a reference to such screenshots (maybe because they are about unfortunate news on a random day), will need to take this into account.
Example:
- The indie app store happens to create app screenshots on a day of a tragic event. (The author-verified app store meanwhile happens to have harmless innocent screenshots of happy events.)
- A reviewer not aware of the auto-generated nature of the screenshots submits a review to the indie app store saying how tasteless it is of the author to choose screenshots of that tragic event to boost installs of their app.
- Without author intervention the indie app store recreates its screenshots for the app at a later stage.
- The author is stuck with a negative review.
In the author-verified app store, if this ever happens (like when the author unknowingly chooses offending screenshots), they can update their app listing by submitting a new version of their app, which stores commonly use to hide reviews for earlier versions.
I reckon this is a bit of a contrived example with overlaps to app version history (which you deal with in a different explainer).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.