12/31/2023 0 Comments Tweetdeck 280 google chrome![]() ![]() If your application has a freemium or free trial, be sure to tell users the differences between the paid and free experience so they’re not surprised or disappointed by functionality that they might not have access to. You should provide a detailed description of your application, including it’s features, quotes from great reviews, information about recent updates, and any other information that might be relevant to potential users. If you’ve already built a landing page on your web site, you can likely leverage what you’ve already written here. This is your space to really excite your potential users about your application and convince them to install or buy it. Detailed Description #īeyond the concise description set in the manifest file, a detailed description can be provided via the Chrome Web Store Developer Dashboard. Currently search sees those two as different app names, and if you search for App2, you won’t find App 2. For example, if your app is named App 2, use App2 instead of App 2. One other good tip - try to use ‘simple’ characters in your application name, and don’t get too fancy including special unicode characters. ![]() In the current UI, the +1 button will also be displayed in this section, another reason to not include tag lines or other stuff in your application name. You must also specify the application name within the manifest file - be sure to specify only the name and not any taglines or things that would be more appropriate for the short description. For example, the description for Angry Birds is simply “Birds! Slingshots! Destruction! Feathers! Fun!” For Gmail, it’s “Fast, searchable email with less spam.” It’s limited to 132 characters, and cannot include any HTML. Use this to tell users about what your application does and why they should get excited and care about it. The application manifest file ( manifest.json) has a property for a short description of your application. I think both TweetDeck and Google Maps do a great job of providing a compelling, and interesting listing, so we’ll use those as our primary examples. Be sure to follow the links for additional resources or details. I tried not to repeat content from the documentation, but instead tease out the important parts or best practices. This updated guide highlights a couple key components of a great Chrome Web Store listing. Let’s take a look at what makes a great Chrome Web Store application listing. People will make a split second decision whether to install your application based on what you put on there, so it’s important to make a great first impression. Your first chance to make a great impression with a new user is often on your application listing page in the Chrome Web Store. I’ll update the screenshots when the new UI launches. Since the consumer UI will change in the near future, I’ve listed my suggestions in the order that they appear within the Developer Dashboard and included screenshots from both the Developer Dashboard and the current consumer UI. I’d strongly recommend updating your assets sooner than later to make sure that when we do roll out the new UI, you’re ready for it, and are looking great. Not only is the new UI a little easier to use and understand, but soon we’ll be launching a new user experience for consumers - which will require new assets from you. A couple of weeks ago, we changed the UI on the developer dashboard and started asking for new screen shots, and promotion images. Tagged Web Design HowTo TipsAndTricks Chrome Web Store BestPractices Web AppĪ couple of months ago, I blogged about the anatomy of a great Chrome Web Store listing - and it looks like it’s time to do an update. The Anatomy of a Great Chrome Web Store Listing (Updated) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |