Here’s a thought from the future:
- The browser is the platform.
- Microsoft has embraced this and has released Office as an ASP.NET 2.0 Ajax application for enterprises.
- Microsoft is continuing its push into ‘Software as a Service’
- You can now rent Office XML Application Server for Windows Server 2007
- All of your enterprise users, using IE7.0, Firefox 2.1, Opera 16, or Safari can now access all their office applications from their desktop. (No, IE8.0 still won’t be out, but Firefox will be at 25% marketshare, and I’m not even going to guess at what Firefox will be alled then — how about ‘Burning Rabbit’ ?)
- Here’s the catch — When users click on that ‘Microsoft Word’ button (or any of the office apps), a local application doesnt load. It loads a rich web application that closely mimics what we now think of as word.
- All of the users have their own document storage on your Windows Server
- All of the users have access to their documents seamlessly through existing methods (the remote storage automatically shows up in a user’s ‘my documents’ subfolder, apple’s finder/searchlight, etc)
- Users can specify permissions on these centrally stored files, and they are easily shared — people don’t have to navigate to a random person’s desktop to get a document they shared, and a person doesn’t have to email it to them. The documents on the server are all searchable by the user’s local desktop (depending on permissions).
- When it’s time to upgrade to a new version of Office XML Application Server, the upgrade is done on the server, once, and all clients automatically have their update.
I know some of this isn’t new OR likely, but it’s fun to take an old idea that was once pure ‘out there’ thinking and bring it down into the realm of “I see how this is possible even if it’s not either soon or likely”
Also, who knows if it will even be microsoft who does this? Maybe it’s SUN, maybe this will all play out on linux desktops first, with “OpenOffice Network Server” — who knows. I think the day of the browser as a platform IS coming, and I think we’re going to see REAL productivity applications created this way, and I think it’s going to come to the enterprise first.
They’re the ones who can see the real cost savings and increased productivity — through ease of deployment and upgrades for the former and ease of collaboration in the latter.
I’m not sure exactly where I got this idea, but I know it’s not my own, so I cede the creativity of the idea to someone else. Actually, I think it was Bill Scott with Sabre / OpenRico on his blog, but again, I’m not sure.
So, you can build a mini application, so what? Well, how about building a “Lightweight Plugin.” Here’s the flow of things:
See, it’s just like having an acrobat reader or flash, but you’ve got ZERO downloads, and you can have it do whatever you want, completely customized to your way of doing things.
But wait, the thing about plugins is that there are only a few of them that people have, so everyone has to stick to using the big ones — acrobat reader & flash. We don’t have to stick to that anymore, since there’s no installation of software to worry about. I keep coming back to “The browser is the platform” — Once you’ve got the idea of the lightweight plugin, it becomes apparent that anyone can just build whatever lightweight plugin they want, and the browser just becomes the platform for running and distributing the application.
The browser is the platform.
The browser is the platform.
The browser is the platform.
We’re not getting rid of regular apps anytime soon, but we’re going to start seeing the web become a very different place, full of big and small applications.
I’ve released a new version of my little Ajax system utility, TopJax The new release displays a bit more information to the user than the last.
If you don’t know, TopJax is basically the unix Top command ported to the web with Ajax techniques. It’s basically a, “hey let me do something that gets my feet wet w/ Ajax while also doing something potentially useful”
I thought this was interesting over on Scobleizer: Apparently Jean Paoli’s team at Microsoft created XMLHttp in 1998 in order to give the Outlook team a way to do Outlook Web Access.
I mean, that’s not all that interesting. It’d be more neat if what we were using it for now was totally not what was expected, but I guess the tool is being used for what it was invented.
Full article about that, the Microsoft Atlas project, which I’m guessing is Visual Web Developer 2005 + ASP.NET 2.0, you can go to ScottGu’s Blog. There, he talks about the upcoming Atlas Client Script Framework, which will provide ajax support to ASP.NET
Next, we need to have System.Windows.Forms implemented in XHTML+CSS+AJAX. Wouldn’t that be something?
- Late 1998 / Early 1999 – Microsoft releases IE 5.0 with support for XMLHttpRequest
- Sometime In Between – Oddpost uses XMLHttpRequest to produce a highly functional webmail client
- February 2005 – Google releases Google Maps to the world demonstrating cross-platform use of XMLHttpRequest (Google also released Google Groups, Google Suggest, and GMail using the technology around this time)
- February 18, 2005 – Jesse James Garrett writes, “Ajax: A New Approach to Web Applications” on the Adaptive Path website.
- The world jumps on the bandwagon, seeing how cool Google Maps is, and that it’s not just “google magic” — the name “AJAX” and some simple descriptions of the technology allow lots of people to really grasp what it’s about.
I’d like to point out that many of the “rich application frameworks” that are out there (many of which are described in my rich application frameworks page) have been at this for a while, working on their technology out of the limelight.
There’s more to this, for sure, but I think i’m hitting the key points.
Some of this was ‘researched’ at various places around the web, but i found the Wikipedia AJAX article very helpful
« Previous entries Next Page » Next Page »