How to Build and Distribute a Force.com ISV app

755ba6ddbfbf90c4a88eb4daf2519dae?s=47 Ross Belmont
September 05, 2011

How to Build and Distribute a Force.com ISV app

These slides were a portion of a session held at "Dreamforce 2011":http://www.salesforce.com/dreamforce/DF11/.

755ba6ddbfbf90c4a88eb4daf2519dae?s=128

Ross Belmont

September 05, 2011
Tweet

Transcript

  1. Building and Distributing a Force.com ISV app Ross Belmont Chief

    Architect @ Appiphony
  2. None
  3. Building for Force.com? Think iOS, not Java/.NET • New programming

    language, APIs and runtime environment • New UI conventions • New distribution options • New quality assurance processes There’s a new definition of what makes an app great.
  4. Don’t build this.

  5. Real World Examples of Different Thinking • Data modeling: an

    Object is not a Table • A user interface that fits with Salesforce
  6. First Example: Data Modeling Declarative Simplicity + Speed Control +

    Flexibility Visualforce Pages Force.com Sites Programmatic Visualforce Controllers Apex Web Services API Web Services API Metadata API Applications Page Layouts & Tabs Record Types Formulas Validation Rules Workflow & Approvals Objects Fields Relationships User Interface Business Logic Data Model
  7. Article Category ??? Relational Object Articles

  8. Defining the “Articles” Object

  9. Categories: An Inherent Attribute

  10. Complex Attributes Are Handled Intelligently

  11. Second Example: UI that Fits Declarative Simplicity + Speed Control

    + Flexibility Visualforce Pages Force.com Sites Programmatic Visualforce Controllers Apex Web Services API Web Services API Metadata API Applications Page Layouts & Tabs Record Types Formulas Validation Rules Workflow & Approvals Objects Fields Relationships User Interface Business Logic Data Model
  12. Reduce Friction For Your Users

  13. Plan More for Non-Development Tasks Distribute Build

  14. PDOs Help, Then Roll Off

  15. How Do We Get Started? • Initial conversation with PDO

    • Communicate the vision for the app • Meet with the team and understand roles • Possible further meetings to discuss requirements • PDO evaluates platform fit and helps build plan to move forward • Initial high-level solution architecture • Validate concepts and design ideas • Plan for upcoming technical and non-technical work
  16. Thank you!