From a coding perspective, I still think the browser as a viable application frame is bunk. Yes, MS has done a fine job of “stateful-izing” HTTP, but it still not a viable replacement for a Windows (WinForms to be exact) application. I have been customizing Time Tracker (an ASP.NET sample app from MS) for use in our organization. I am about to split the middle tier, and data tier components away from the UI, and recode the from in WinForms.
There are enough really good 3rd party controls available, so I can just simply plug-n-play my front end together. The logic and the business rules are all in place already. Also, the concept of tabs that the web app makes use of can be implemented way easier in WinForms. To further ease ongoing development, I can achieve real DataBinding in a WinForms app that I can’t get in ASP.NET.
Hey, not to put down ASP.NET, but I need my app to do exactly what I want it to do, and not have to settle for the idiosyncratic behavoir of a web browser. I will however continue to develop the mobile portion of the app. I plan on breaking the middle tier away using remoting. The ASP.NET app can speak to the middle tier the same way. I assume I will be using GenuineChannels for the remoting underbelly. Dmitry Belikov has done extensive work with streamlining .Net remoting for effeciency. The commercial vesion includes source and is only $99.95 (Dmitry, you should sell it for $105, people would pay it).
I’ll put up some screenshots when I’m ready.