Raven - a Mac site-specific web browser
raven.io
raven.io
"Raven uses a technique called "site specific browsing" to create a dedicated browser instance for certain websites and their features. It debuts with the most widely used websites including Google+, Facebook, Twitter and Quora. Within each app Raven provides yet another instance for key features. This provides a whole new level of multitasking within a single window. The Smart Bar unifies navigation across many different websites allowing access to features quickly, without effort and with little instruction."
I have no clue what this means. This clearly needs to be dumbed down to be understandable by average users.
From the Fluid website: "Turn Your Favorite Web Apps into Real Mac Apps"
Not fully accurate but easier to understand.
With that said I don't think that's at all clear from the copy... just what I'm inferring.
When you add the twitter web app it lets you click replies and dm's in the fashion that fits with the trend those apps brought. It's the same for Facebook, techcrunch (tv, other elements) and hackernews.
It's a nice idea although is slightly annoying unless you're on superfast internet as unlike those other apps you have to wait for your internet to catchup.
I think this browser needs speed increases as unless it's the fastest browser or on par it has little point. Interesting idea but not intuitive enough for me.
People still use Rockmelt so there must be a market for this.
Between the misuse of software jargon, the buzzword overflow, the overall site design, and the potential for abuse I'm having a difficult time trusting this thing with my data.
Sort of like a dedicated area in the browser that a webapp can add site-wide or page-specific UI controls to, rather than have them anywhere on the page?
Basically, the webapp equivalent of the OS X File Menu or Inspector. That's an interesting concept. Nontrivial chicken and egg problems though in terms of adoption. One approach is a Chrome extension that uses JS to add a "<nav>" element on the left hand side for a select list of sites. The idea is that over time, other sites could adopt this convention and your wrapper might not be necessary.
But are you thinking that you will always want to display these new UI elements in something that is not HTML/CSS/JS? Hmm. Unless you can do some sort of "automatic extraction of UI" from a page...which could actually be super interesting, as the homepage, sign-in button and so on aren't always that easy to find.
That's the sort of thing one could see a browser taking over in a left pane till the site owner got their act together.
Unified with who? If I'm AnnoyingSocialSites.com's competition, why do I want to unify with them?
Beyond that, what are you providing that can't already be done in a standard browser?
It seems like most of the functionality you're providing is already available in Air or Titanium.
So this is a lead-generating and advertising business model? I agree with the other posters that the value proposition based on your website is still a little vague.
All that said, changing the BROWSER of a user causes a whole bunch of other problems that you will run into.
First, you want to reduce friction of web-service adoption, but require that users change their browsers first? This creates friction where there was none before. A vast majority of internet users still use IE because they think its the internet - not because they made a conscious decision. Its clear you will miss these users (not just because its Mac only).
Other segments could be blocked by IT departments, internal web-app support (I only assume you mask webkit somehow?), or the choice of browsers already installed by other users (kiosk, family computer). Most of the consumer market is covered web-service wise with GMail, Dropbox, and Facebook. Most of this market uses the services their friends use, not something an esoteric browser will suggest to them.
There are other businesses out there that help you 'discover and sign up' for web-based services, including but not limited to getapp.com, appdirect.com, and more integrated solutions with identity management and SSO for organizations.
Now that you have your beta - don't be too inclined to start building complex discovery features that no one will see. Adoption of your browser as the top of the funnel is your primary goal. You first have to overcome reasons to use Safari, Chrome, or Firefox with a unique value proposition they could only get through your browser. Right now a user can use Chrome and go to one of those sites I mentioned and they never had to download and install your product to do it.
I understand the 'lets flip it on its head and get them at the browser level' but thats a war usually fought for different reasons, requires a level of investment probably not worth what you are trying to do with it, and all during an era where desktop browsing is declining in favor of mobile-web and native app experiences are taking over.
Still, I could have completely missed the reason for Raven and what it is trying to accomplish and my response is only based on my experience so YMMV.
IE may be the most popular browser, but it's not used by the vast majority.
Being able to create an app on the fly would be nice though I can see the merits of the app submission process.
The amount of controversy generated here probably means your idea is worth exploring further. Best of luck.
The only thing I do not like so far is that I can't use mouse gestures (three finger slide) to navigate back/forth like I can in Chrome. I'm addicted to that feature.
The sentence "We have finally started to make sense of the differences between Bookmarks and Favorites." bothered me.
I find the difference between a typical browser's bookmarks menu and its bookmarks bar quite clear. The menu is reference for later, the bar is everyday items.
My bookmark bar is cruft free, no favicons, just lowercase abbreviations for bookmarklets and one or two uppercase letters for often used sites:
read paper pin j.mp P Y TM LF G R A O T G FB F
For example, Y is this site. If I have too many to fit horizontally, I look for whichever ones I haven't been clicking and thin them back out.My point is modern browsers all have this difference: visible daily use bookmarks, and bookmarks menu bookmarks, and there is a difference between them.
The concept makes perfect sense ... to me anyway. Having the 'web apps', with their own unique drop-down context menus only a click of a button away makes for such an awesome alternative to wasting time looking for appropriate links/buttons on websites.
The potential for making a user's web-browsing experience less cluttered and more organised is definintely there.
Looking forward to see where this is at in six months.
We are considering making an iOS app that will sync with Raven for Mac, and maybe later some ports to Android and Windows.
We don't have any plan to open source the project at the moment, as most of the code is linked to our UI and very specific, currently we use the webkit version installed and your Mac, s tied to Safari (and act the same as Safari too), that why our download is so tiny. When we will start our own fork of webkit we might consider share the sources as it will be interesting.
But if you want technical details about our Smart Bar UI for example I'll be glad to anwsers your questions :)
I noticed yesterday that Fluid uses the Safari cookie store - which makes it useless atm as a private browser.
Quite often people will browse about one topic and then want to go to one of their other sites to get a different perspective, or to watch a video of it etc. It would be good if there was built in "search" where it can work out what topic you are reading and automatically search your other main sites for the same topic. Then you can click between your main sites to get each perspective/content on that topic.
Filling web forms? Sign up? This problems are trying to be addressed by SSO using providers like Twitter, Facebook or some new kid in town with OAuth/OpenID/YouNewHipsterProtocol.
The idea of having a Site Specific Browser was to have a independent "browser" just to go to X site and be encapsulated from crashes or oddities from plugins from your main browser. It may also have some nice OS specific eye candy or features like system wide shortcuts.
Not becoming the web on training wheels.
But please, don't close all websites when I close the window. Closing tabs on closing the window makes sense for Chrome, where each tab represents something ephemeral to begin with. But in Raven, a "tab" might be my Twitter page or my Hacker News feed. I want that to be readily available when I reopen Raven. (For the time being, I might just use CMD-H instead of CMD-W)
Or maybe that is not what Raven is intended to be after all?
We have a lot of to consider, we don't want to provide a too limited experience, that why at the moment Raven behave as other browser, but we will adjust it soon.
But that creates an interesting problem: Twitter and Gmail will auto-reload its contents. Hacker News will not. Therefore, I'd like to set some fixed auto-refresh interval for the HN "app" (but not Gmail).
I don't know whether that is in line with your vision for Raven, but it certainly is something I would like!
Additionally, I'd like to have the option to open external links in my regular browser.
Last I looked at Fluid, it had a whitelisting feature but it was horribly broken in that it included default rules that were irremovable like 'userscripts.org*' allowing 'userscripts.org.evil.com'.
I haven't looked at Raven yet, but hopefully it has whitelisting that works. That alone would make it worth looking into for me.
I didn't quite get why there are "apps" and why they need to be installed. Why are these more than just regular bookmarks?
That needs a better explanation.
Basically, I love the left side of Raven. I don't like the tabs and address bar...
but i don't get raven's USP
"The web has been plagued with required forms fields when signing up for websites, apps and services. While auto-fill is helpful it hasn't made the process of signing up for services any easier. Smart Bar apps provide us with a 1-click process for adding an app to your browser. When we combine this with an API for developers to integrate their "Best Offer" with subscription services we can provide a 1-click sign-up and subscription management just like you can with other software."
> The web has been plagued with required forms fields when signing up for websites, apps and services.
The solution isn't yet another standard (cue XKCD comic)—we already have OAuth, OpenID, and BrowserID for authentication.
> Smart Bar apps provide us with a 1-click process for adding an app to your browser. When we combine this with an API for developers to integrate their "Best Offer" with subscription services we can provide a 1-click sign-up and subscription management just like you can with other software
A proprietary API usable only in a new OS X-only browser? Have you approached the Mozilla Foundation?
FWIW, when I looked at Raven, my initial thought was "it's a browser with app tabs on the side". It's nicely designed, but doesn't seem groundbreaking to me.
I do like the Instapaper integration, though! I also like people exploring new browser ideas.
(obdisclaimer: I work for Mozilla)
Lol, most widely used websites? Maybe for tech geeks. But for the rest of the world, it's Facebook, Craigslist, YouPorn/PornHub, etc.
You're welcome.