Enable you to win more customer’s who have specific needs. It may seem common sense, but introducing fields of wrong data types, or junction objects at the wrong hierarchy level etc can create a very confused and rigid architecture constraining your customers ability to develop and grow. As a

In our last blog, we looked at ensuring our code was streamlined and efficient, but we also need to look at the technology that we use to develop and deploy the product. Many solutions can be developed to solve the same issue and although each often has pros and cons, often there are obvious techno

ISV customers demand more responsive products, especially when they are paying for them and if the code is efficient and streamlined the Baseline product will be easier to expand. Having made the code improvements we have made, our app is now working well, with no exceptions being raised by gove

Security is paramount to any new product and if the levels are not sufficient, they will not pass Salesforce’s stringent checks. But what can you do to ensure you achieve these levels? Continuing with our scenario where we have now developed a very good robust ISV app that can cater for almost

Without quality code development, it becomes more difficult to expand your product as your requirements build, not to mention it won’t pass Salesforce stringent checks. If we take our working example that we mentioned in the first of this series of blogs, we decided to build an additional

Protect against governor limits. Without protection against breaching Governor Limits, a product will not pass Salesforce’s stringent checks, but how can avoiding these limits help to deliver a good PDO experience? Rather than talk about technology, lets work through an example. Let

In the slightly hectic build-up to Salesforce World Tour this week, there are many meetings taking place in London with teams of ISV’s, SI’s, developers and anyone with an interest in Salesforce descending on London to find out what the latest developments are in the Salesforce world. No

Product Development Outsourcing (PDO) is traditionally understood to be the outsourcing of the technical design, development, QA, delivery, support, maintenance and even the client implementation of a software product from a product vendor to a software development vendor, or the outsourcing of dif