Design Process - Online versus Offline

I'm in the process of spec-ing out a rich application for personal finance management - a cross between tools like Quicken and Mint.com and a set of spreadsheet macros I created for personal use. It would be a simple matter to build it either online or offline (preferably both), but we all need to start somewhere.

So what's the best way you choose deployment focus with your projects? Do you deploy a desktop app for testing first and evolve to a rich, online application later? Or do you build a web-based system first and package it for desktop deployment later? Both are valid approaches, but I want to know which has proven the more efficient in the past.

In either case, the application will still be built somewhat the same - a separate database layer, business logic layer, and presentation layer. 开发者_开发知识库The question is more about the location of each (local or remote) and the problems that might arise by choosing one approach over the other.

In my opinion, a Rich Internet Application only makes sense if there is a web service tie in. If people will be storing their personal finance information on your server, then it makes sense to have a RIA, otherwise, it sounds like a desktop application solution.

For the rare case where you would have both, the web application is usually limited, but provides a zero-install or cross-platform solution. Consider online word processor applications versus their desktop counterparts.