Hi,
My ambitious and innovative
project and its extension
SmartyList (
http://bit.ly/SmartyListApp) having tough time in getting it published and I am wasting to lots of efforts in trying to justify again and again to Chrome dev team.
My last subsequent packages were rejected to publish stating it is against "Spam and Placement in the Store" which states:
* Do not use irrelevant, misleading, or excessive keywords in item descriptions, titles, or metadata.
* Please ensure that your item has a description that clearly and directly relates to its functionality.
In email they say “Do not use irrelevant, misleading, or excessive keywords in app descriptions, titles, or metadata”. It is not making any sense because my latest package contains the minimal information for the users as below:
Manifest.json:
Title: “SmartyList”
Description: “Helps you save favorite information and links in an awesome and interactive way.”
App’s Dashboard Description:
“SmartyList is an innovative information shortlisting tool live on the websites intuitively as a Universal List, and are accessible across other websites as one common list. \n\n Currently, it works on Amazon, Ebay, Facebook, Twitter, Instagram, Linkedin, Youtube, Pinterest, and few more as listed here at
http://smartylist.com/platforms.html. \n\n Why it requires read/write access?
Because it needs to process the content directly on your site and then writes/displays Shortlist buttons and its UI panel. \n\n For use cases, screenshots, demos, help or FAQs, visit -
https://smartylist.com/links.html”
Other extension which seem to have no objection on the same policy, why and how?
So, can you please answer these and help me out publishing it?
1. What keywords do you think irrelevant, misleading, or excessive?
2. What part of description is not clear and not related to functionality?
3. Why can’t your review team be specific to the issue with exact details, instead of relaying on your abstract policies?
4. Can you define or document some where about the definition and examples of irrelevant, misleading, or excessive keywords?
5. How do you prevent this kind of inefficient reviews from your team going forward?
Please respond me in same order or questions, and let me know when you can review my latest package and approve it if you find everything is good, if not please let me know the specific action item that I can take care of and let the developer community learn and follow it going forward.
Thanks