So if you live on the bleeding edge, you probably have heard all the buzz about how site specific browsers are going to be the future of internet sites. Ok, a little background for those only living on the cutting edge, a site specific browser is a browser program (like IE/Firefox/Safari) but built with functions specifically for a site (example Mailplane). Typically these “browsers” are built off of existing browser development code (Webkit) so that author isn’t writing a browser from scratch but really just tailoring the browser for specific functionality for that site. So whats the difference between a site specific browser and a stand alone application? Well the idea is that the web app is still accessible via the web (unless we get some really crap web app designers) via a normal browser but is enhanced via your site specific browser. So Mailplane for example, you can check your Gmail from any computer with any browser, but using Mailplane might make it a little easier and you would want it if you are in your “home” environment.

So I have drank the koolaid and been using Mozilla’s Prism for a couple of key web apps (Google Reader, Gtalk Gadget, Campfire) but right now Prism doesn’t offer me any advanced functionality more then I have the ability to restart Firefox as often as I want without interrupting my Podcasts from Google Reader or shutting down my chat sessions. Its great and I am sure that people will take Prism and run with it and create some really cool site specific functionality.

SO, what could I not want with that? Well here lies the problem. I am willing to say have 5 different browsers on my computer open at a time… max. So we have my regular Firefox, Google Reader, Gmail, Campfire and Gtalk Gadget however I crave site specific functionality on sites I don’t visit as often (Google Calendar, Del.icious, Ma.gnolia, Remember the Milk, Pastie, Facebook… the list goes on and on and on. I am not willing to go through the process of installing site specific browsers for each of those sites or it wouldn’t even cross into my mindset as I am surfing to be like “oh I am headed over into Facebook so now I should open FaceBrowser. What I want is a slightly modified solution of site specific toolbars. Now my screen real estate is KEY and at maximum I allow for 2 toolbars to be open at any given time (and about 5 buttons). What I am looking for here is to have dynamically switching toolbars per site. When I go to Facebook, I want the “site specific toolbar section” to go to the Facebook Toolbar that allows for all the additional functionality (not to be confused with a toolbar that checks like Facebook status that I may want open when I am on other sites). What I am imagining here is like when I am on a fan page or cause that it would have a drop down where I could just check off friends to invite and things like that. We are talking like Flockish functionality but with some sort of API that when visiting the sites the site author can say “I have a site specific toolbar” (or even maybe more then one… standard and power user?) and give the user the option to add it.

Now Mozilla has released a new project called Weave, which granted I haven’t done as much research as I want, looks as thought it will offer me the ability to like create an account at Mozilla and add the toolbars I want and then when using their browser on different computers will give me the ability to sync up my extensions (which I assume will contain these site specific toolbars) and any other customizations I am talking about. So now I am syncing up my site specific browser needs (obviously as long as I use Mozilla - but I am sure other browsers will follow).

To sum it up, while I like the idea of site specific browsers and will definitely use them, the following issues concern me:

• Extensions : Is it all or nothing? Will I be able to use my Milk extension with my gmail browser?
• Security: Do I now have to worry about site specific browsers reintegrating security fixes in their code?
• Integration: Will the integration with a site specific browser be seamless? ie can I say all Facebook goes to my Facebook browser and even if I am surfing in Firefox links to Facebook will open there? Or do I have to make a specific effort.
• Business Model: How are the developers going to make money? Do I need to start reading privacy agreements in serious depth (yes I know I should be anyway) looking for lawyer jargon for “we now have the right to copy your data” or am I thinking I am now going to be shelling out a couple hundred bucks a year for browsers?

Anyway, there is my thoughts on the matter, and while I don’t have enough programming skill or time to take on such a task, if someone reads this and does I would love to brainstorm about it.