Safari Develop Menu

Do you want to see what an iPad user sees when they look at your website? Well there is a simple way to check it out without buying an iPad on either Windows or Mac:

1. Download and install Safari (if you don’t already  have it)
2. Edit -> Preferences (or Safari -> Preferences on a Mac)
3. Go to the Advanced tab
4. Check the “Show Develop menu in menu bar” option
5. Close the preferences window
6. A new “Develop” menu option will appear
7. Select “User Agent” and then “Mobile Safari 3.2 – iPad”

It isn’t perfect (hard to simulate rotating the device) and you should also disable Flash, but it gives you a rough impression.

Now I am a big fan of constant change, I just felt that developers were being given tasks that (despite being scoped user stories) still contained a large number of unknowns. I didn’t know if I trusted them to call me in when they got stuck, rather than finding the quickest route themselves. Additionally the roles of Project Manager, Product Manager and Development Manager were stepping on each other’s toes. Normally I am happy to write the requirements up front and then manage the project. Now there were no complete signed off requirements documents, project management was on a wall and the development team was in control. What am I meant to be doing? I am not someone who likes to sit back and wait to be called upon! I eventually found the following presentation, which was literally one of the only sources I can find about how Agile development management is meant to work:

Even though I am only just beginning with Agile I felt the presentation gave me a good sense of where I fit. What are your experiences in Agile management outside the development team?

What did I like?

This book gets straight to the point, there is no bullshit whatsoever and it makes no apologies for that. Equally there is no room for bullshit in the product; decide a goal, keep the budgets tight, keep the team tighter, listen to the customer (at least when they bang down the door) and just execute the hell out of what you are doing.

This book is a reminder that building a product is not just about technically executing. Many usability, sales, HR and marketing issues must be addressed to deliver a successful, well-rounded product. You need to reflect this well-rounded nature too, everyone should take support calls, think of usability, write blog posts etc.

What didn’t I like?

There are however some minor things I don’t agree with. I think exit surveys are valuable, there should be a formal suggestion gathering and prioritisation process and there is a limit to how much information you should place online. If you have a mass appeal, generic app then I think these rules are a little different to someone developing a niche app for a specific market. Apart from these few items, I was nodding the whole way through the book.

Conclusion

This book embodies the entrepreneurial spirit of today’s web app developers. Put your heart into the app, and then put your app out for everyone to see. If you are a motivated person who wants to focus your vision and energy, then this book is for you.

1) Export the certificate from the original server:

Export-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -BinaryEncoded:$true -Path c:\certificates\export.pfx -Password:(Get-Credential).password

http://technet.microsoft.com/en-us/library/aa996305.aspx

2) Import the certificate into the new server:

Import-ExchangeCertificate -Path c:\certificates\export.pfx -Password:(Get-Credential).password

http://technet.microsoft.com/en-us/library/bb124424.aspx

3) Enable the new certificate:

Enable-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -Services “POP, IMAP”

 http://technet.microsoft.com/en-us/library/aa997231.aspx

Done!

Internet Cash Machine

The core promise of SaaS is that it will help you deliver services more efficiently. Instead of trying to manage software projects (which can easily get expensive and out of control) a company can outsource non-core development and deploy an SaaS solution almost instantly. In the current economic downturn many people have been watching SaaS vendors closely to see whether they struggle or thrive. On paper they are cheaper and allow businesses to focus on their core strengths, but would companies shun the risk and element of change in uncertain times?

There have been a few earnings announcements over the last couple of months that are proving the SaaS backers right. Salesforce is the biggest ‘flag bearer’ for SaaS solutions, and it has exceeded analyst expectations and posted a 43% revenue increase from the same quarter last year. The good news doesn’t end there however. Concur, Taleo, RightNow and many other SaaS providers are also posting record quarters.

There was one flow of logic which struck me in his speech. Moore’s law is still holding true, and computer hardware is continuing to double in processing power every 18 months. This computer power is also appearing in more and more locations. But when was the last time your network doubled in speed? What about doubling in speed to each additional node? This rapid processing power increase has meant two things that are obvious even today:

1. Computers are islands of computing power – There is no seamless transfer of data between your devices. You work on a file at work, email it home, download it at home, work on it and send it back.
2. Deploying local machines is too hard – Each branch office needs a rack, servers, backup, redundency, configuration, support, licencing…

Microsoft’s solution at a high level is the Mesh stack, the structure of which can be seen in the slide shown here. The fundamentals are that local software is fast, hosted services are convenient, so lets tie them together with an API and we get the best of both worlds. The trick is getting the balance right, where does a local application end and the service begin? How do you split the business logic? How do you provide offline access and quick sign-on to new devices? Hmmm…

Microsoft’s current practical solution is to re-write most of its server packages to allow hosted delivery. Hosted Exchange is an obvious flagship for this. Google have taken a different approach. They believe that all you should need on your desktop is Chrome, essentially an all-purpose thin client rather than a thick client on a drip feed.

So who is right? Well I am betting things will converge on a middle of the road approach. Implmenting with current technology I would say that javascript, a web browser and some sort of XML interface would be the best way to go. A few things need to develop from here:

1. API’s need to be standardised and built into the browser (or OS as these merge). Something like Javascript libraries, but compiled, lightening fast and highly reusable. Chrome is getting there.
2. Data transfer needs to be better than XML. Think highly compressed, encrypted on the fly, but quickly decoded into a human readable format if necessary. Microsoft’s MeshFX is getting there because it has authentication and other services built in, but it needs to be open like SOAP.

So I guess the race is on! Google will take Javascript to it’s limits, Microsoft will try to blow us away with it’s feature set. When will they sit down and standardise on the next generation of javascript and data format?

One of the most interesting statistics for me was that Salesforce.com (one of the few genuinely profitable SAAS success stories) spends half its revenue on sales and marketing. When I think about it it makes sense, but I guess coming from a technology background it isn’t something that I would have initially thought of. The scary thought that comes after this is what percentage of revenue is taken up once you include support as well? The even scarier one is are you really achieving scalability if these represent the vast majority your costs?

As the article points out, there are three economic fundamentals:

1. How much it costs to attract new customers (known as subscriber acquisition costs)
2. How much money can be extracted from those customers in regular subscriptions (known as “average revenue per user”, or ARPU)
3. How often subscribers drop out and have to be replaced (the churn rate)

For point 1 I think SAAS companies still rely on their old mantra that the SAAS model generally is still struggling for widespread momentum. I think this still holds true, but perhaps these days more because of the costs of migration and training rather than lack of market acceptance or knowledge. The sales and marketing costs are therefore quite high as they are pulling lagging and inflexible customers into what is now a competitive market place with low barriers of entry.

These low barriers of entry tie into the last two points. Companies can theoretically treat SAAS software like they would their telephone company and switch at any stage. This means that new entrants can come in and undercut the established players, keeping subscription revenues down across the board.

The interesting part for me is that online classifieds is somewhat like the SAAS model. It relies on subscriptions and has a low barrier to entry. Why are they so profitable then? I have a few ideas:

• A new twist on the established classifieds model, rather than a whole new model
• Industry maturity leading to a consolidation of players (and profits)
• The difficulties in targeting consumers online

To be honest I really feel like I am missing something here. Can anyone help?

It also helps explain my point, the GPL isn’t the Open Source saviour some people think it is. I hate to list points, because the people feel they need to find a way to argue against each one rather than the logic as a whole, but I am going to do it anyway:

1. Money = Evil – Any efforts to profit from Open Source development work is treated with scorn. Comments such as “To release a non-free program is always ethically tainted” frustrate me. Equally promoting an Open Source product does not give you licence to trash commercial software. They are your competitors, if you think you are on their level then treat them with respect.
2. Discourages Integration – The GPL is brilliant for making utilities. Compilers, databases and graphics programs are all essentially utilities that you interface with in a certain way, but never extend or deeply customise for your own purposes. Deep integration is one of the biggest competitive advantages that Open Source has over commercial software packages, so why make it hard? For example SugarCRM allows web service integration; but even modules, templates and dashlets that integrate within the existing API’s are considered to be covered under the GPL. Is this really a deep extension of the core product?
3. Patent Protection – Patents are either loved or hated, usually depending on whether your name is on one or not. Regardless, the fact is that they are not going away. Open Source products are just as vulnerable to patent infringements and litigation as commercial software is. As the lines between Open Source and commercial work continue to blur, it is emerging that corporate indemnification is almost becoming a quality assurance stamp. A community cannot offer indemnification, so they really need to focus on their competitive advantages. Stay away from heavy duty licences that just muddy the waters for smaller businesses and institutions, don’t forget a hatred of licences seeded your whole industry!

As with anything legal there is no ironclad solution. As far as I can see the solution is to make it as easy as possible for people to contribute maximum value with minimum overheads and receive value for whatever purpose they desire. Rely on the fact that producing a commercial product that is 99% Open Source is not a safe, competitor-free business model!