Originally posted by zathras
I'm writing it so the next big thing will be the NBT.
Seriously I am spending time on something but I think the next big thing will be integrating data a website and desktop applications.
So lets say I am analysing the quarterly sales figures. I can go to a website to see them, import them into Excel. Work with them, maybe change some budget figures and then when I visit the website the data will change.
When I go home I can go to my PC at home, and open up and see the same data.
What I mean essentially is that a major part of an application will be provided via Web Services. This means that coupled with One-click deployment, there is no such thing as an upgrade. It all happens seemlessly, all I do is confirm that I want the upgrade done.
Any application with a heavy data input can be implemented this way, even document storage.
Tale for example Payroll. I've supported them and every year their is the same activity that can become a royal pain in the rear-end. Between the March Payroll and the April one assuming they straddle the end of the financial year, NIPAYE tables need updating. If you support Sage for example this may mean travelling around all clients and invariably some twit has corrupted the database so that will need repairing. I did this every year for 4 years and it is a pain.
Web based software would avoid both these and in addition corruptions cannot be caused by the user pulling the power because in the web the user is never actively connected to the database.
Seriously I am spending time on something but I think the next big thing will be integrating data a website and desktop applications.
So lets say I am analysing the quarterly sales figures. I can go to a website to see them, import them into Excel. Work with them, maybe change some budget figures and then when I visit the website the data will change.
When I go home I can go to my PC at home, and open up and see the same data.
What I mean essentially is that a major part of an application will be provided via Web Services. This means that coupled with One-click deployment, there is no such thing as an upgrade. It all happens seemlessly, all I do is confirm that I want the upgrade done.
Any application with a heavy data input can be implemented this way, even document storage.
Tale for example Payroll. I've supported them and every year their is the same activity that can become a royal pain in the rear-end. Between the March Payroll and the April one assuming they straddle the end of the financial year, NIPAYE tables need updating. If you support Sage for example this may mean travelling around all clients and invariably some twit has corrupted the database so that will need repairing. I did this every year for 4 years and it is a pain.
Web based software would avoid both these and in addition corruptions cannot be caused by the user pulling the power because in the web the user is never actively connected to the database.
Comment