5 responses

  1. dpilling
    October 26, 2009

    Nice post Ben. There is certainly a lot of diversity in platform approaches and your taxonomy is as good as any I’ve seen.

    Personally, I prefer a business definition of platform to a technical one, because the technical is too hard to pin down.

    I see platforms as business models that enable two different groups of customers to collaborate in ways never before possible. The typical goal of platforms is either 1) Matchmake, facilitating transactions (eg. buyers/sellers, information creators/information seekers, 2) Aggregate and monetize audiences (eg. google, publishers) or 3) minimize costs (eg. operating systems, cloud dev. platforms).

    For me, its just easier (and more insightful) to understand the business function of the platform than the technical function. The prior should determine how the latter is executed.

  2. dfowlie
    October 26, 2009

    Just to build on your comment about Force.com dictating look and feel of applications on their platform this is entirely up to the developer.

    Most developers stick with the default look and feel because it reduces development time significantly and provides a consistent UI across developed interfaces and those built into the platform.

    However if a developer wants to code all the UI they can do just that. For some of the best examples of UI’s on Force.com that have a totally customized look and feel look at: http://www.modelmetrics.com/services/salesforce-crm-and-forcecom/forcecom-sites-ecommerce/

  3. Ben Kepes
    October 26, 2009

    @Derek – thanks for the feedback
    @Dan – cheers for that – point taken about the customization of force.com sites…

Back to top
mobile desktop