Please Login with your Salesforce ID to post, promote or comment.
Salesforce IdeaExchange
FAQs | Terms of Use7409 Ideas; Promoted 154857 Times; 14441 Comments.
- Suggest a New Product Concept
- Promote Ideas That You Want to See Developed
- Discuss With Product Managers and Other Users
- See What We Are Planning To Deliver
AppExchange Directory Ideas
What feedback system do you prefer?
Please comment on this idea if you have any feedback. Also, vote for this idea if you'd like to see changes to the current star and review system.
Subscribe
The AppExchange should recommend apps just like Amazon.com
When I go to The AppExchange it should remember me, know what Apps I've used in the past, know if I'm a customer, and recommend Apps that are suitable for my profile and what customers like me have done in the past.
This is exactly how Amazon works and it leads me to be a much more successful buyer. The amazing thing about the AppExchange is that it knows more about me than Amazon. The AppExchange knows if I have actually USED an App that I downloaded and how I've used it. Amazon has no idea if I read the books that I buy.
The AppExchange should be able to provide even better recommendations than Amazon because it's a multi-tenant system.
Make managed packages less restrictive / more intelligent
Making an application "managed" is a big step. Immediately several items become frozen and fixed for all time. Although many of these make sense to permit upgrades, many are unreasonably restricting and do not allow for "normal" evolution of an application over several versions.
Take one example: the text comments in a help popop on a custom object field. They can't be altered after going managed. If user feedback says that the comments aren't helpful enough - tough luck. If the use of a field changes - again tough.
This example is one where the AppExchange system could permit the developer to make the change in the package - and then all future installations of that package have the new text. Anybody that has already installed that app and customised the popup help text would keep that customisation. The change to the managed package would only affect new installs.
There are several examples of the above intelligent approach to managed package upgrades.
Another big example is to permit items to be depreciated. This includes custom objects, fields and scontrol. These would be flagged as "no longer used". Or better still, not included in new installs of the package. Like the previous example older installations would not have the depreciated item automatically removed (although they could be given to option too if they wish).
Free and Discounted Apps for Nonprofits
It would be great to be able to search for Apps that are free or discounted for Nonprofit Organizations.
Under My Filters/ Additional Filters adding:
1) Free for Nonprofits
2) Discounted for Nonprofits
About Tabs Not Included In Tab Quota
AppExchange packages include "About" tabs as a courtesy to help introduce customers to an application and inform them on its usage. These tabs are often the first to be deleted once the tab quota is exceeded.
Propose the use of a "Tab Type" field during packaging that identifies a Tab as purely informational and not to be counted against the organizations total Tab count.
Show # of Current Installs on AppExchange Listing?
Partners - Are you interested in showing on your listing page how many actual installs/deployments your app has? For downloadable client desktop apps, a "Download" # could be shown in place of the Install metric.
AppExchange help for novice users
At the end of ever application install in AppExchange, the user is presented with a page of "Final Steps". This page is all text, provides little help, and can be daunting for users who are not yet be familiar with Salesforce terminology.
A simple improvement would be the addition of links on each of the steps which take the user to the appropriate configuration or help pages.
The Formula Field Exchange
What if there were an area on AppExchange for Formula Fields that was INTEGRATED right into the wizard used to create Formula Fields?
Who knows more about how to write formulas than ALL of the other formula writers using salesforce.com?
Writing formula fields isn't easy. Sometimes that's because you can't think of where to start, sometimes it's because there's a trick or approach that you haven't seen before. If you could leverage the great formula fields written by others you'd be much more likely to be a successful formula field writer.
AppExchange standardized packaging of App config/properties
It would be nice if we could provide a (free as in edition limits wise) special custom object per AppExchange app installed for configuration properties of the application.
Giving developers the ability to store Application configuration as custom fields on this object using any or a subset of the available field types.
The record type (a singleton enforced by a trigger) for org wide configuration, the second record type for user specific configuration, so values from this are both available as global merge fields for the developer. And can be easy configured/adjusted by the admin, having an consistent ui/interface to this objects edit view via the setup admin area as well as audit trail of changes made.
Many apps implement the org wide config with a custom object storing key/value pairs and a custom scontrol ui, and then user specific config as custom fields on the user record which is fine, it would just be nice if we acknowledged this need for storing application preferences/properties and provided a more standardized way of achieving this.
Being able to set default values when packaging applications would be a logical enhancement to this functionality as well.
The object names could be easily generate e.g.
config_namespace__appname__c
As well as the global merge fields:
{!$Appname.Property}
Perhaps just making this another benefit of managed packages initally would be the right approach.
Compare Apps
Add the ability to compare two or more applications on a standard set of characteristics, for example: description, price, support, rating, certification, etc....
Package Record Types
It would be great if AppExchange packages included record types.
AppExchange: Voting or Stars, Reviews or Discussions?
What app rating system do you prefer?
- The current 1-5 stars system.
- The current 1-5 stars system plus the number of reviews in the search results.
- A voting system where you can vote up/down on an app. The number of up/down votes displayed in the search results.
What feedback system do you prefer?
- The current review system.
- A discussion board system where people can leave comments and others can respond to them.
Please comment on this idea if you have any feedback. Also, vote for this idea if you'd like to see changes to the current star and review system.
User review responses
As a partner we realize that we will get negative reviews but currently there is no way to respond to these reviews in a constructive way without compromising the trust of the community. It would be great if a partner could respond to a certain user review on their listing page so the larger community could benefit from the exchange and get a taste of the partner's customer service chops. Ideally it would be more of a discussion board for the particular product.
Subscribe
POST IDEA
TOP USERS