chris_lacy

What services are you talking about? The history Android permission, or something else? Certainly I don't think there's any such API for Chrome.

Definitely shouldn't be. DM me on Twitter (@chrismlacy) if you like and I can take a look at what might be going on.

Yes, it's closed source. I can't see a realistic alternative to this given I'm trying to make a living selling the app.

But FWIW, I can promise you I don't transfer your browsing history. My policy on such data is I simply don't want to ever have a copy of it. If that means I can't sync your history between Link Bubble installs, so be it.

Change the Settings -> Left bubble value.

I already have the code to allow you to specify this via Link Bubble's settings, but I've opted not to enable it so far.

I tend to subscribe to Apple's philosophy of trying to avoid adding configurable options unless absolutely necessary, but frankly, that position can be a tough sell to early adopting Android users.

As I said above, Link Bubble development started before I was aware of Chat Heads.

I see Link Bubble as an additional application rather than a complete replacement for your existing browser. Drive the Prius (Link Bubble) around the city during the week, take the truck (Chrome) out on Sundays.

I'm talking about the interface that presents the web to the user, not the underlying method of rendering the web.

Many thanks :)

I assume because they use the t.co link to verify items have been clicked for their ad services, but I can't be sure. Either way, as I user I couldn't stand that wasted time, so I went about trying to fix it.

As I said in my post, I definitely thought long and hard about the implications of applying for such a patent. Your points were definitely at the forefront of my thinking.

In the end, I concluded that Loren Brichter's pull to refresh patent proved rather valuable, so I might as well not close the door on such an opportunity myself.

Link Bubble won't throw out those resources, so the page(s) will still be there.

FWIW, Link Bubble development began early last year before I'd heard anything about Chat Heads.

Thanks :)

What stores do you mean?

Yes, further optimizations are necessary. It's V1, and I needed to get it out to see if the app would be well received first. That said, I do envisage Link Bubble will be used more to quickly read a few links rather than keep 40 tabs open at once like Chrome.

What is an example of an app you'd rather load in Chrome rather than Link Bubble?

It requires Jelly Bean or later.

Figuring out the line between free and Pro is always a challenge. I think the value proposition is clear from the free version, but I'm always listening to opinions otherwise.

Link Bubble uses the Android WebView for rendering, yes. But the API is pretty deficient in a few key areas, and I will likely have to switch to a custom modified version of Android 4.4's WebView at some point.

This, as well as staring a Chrome waiting anywhere up to 5 seconds or more for t.co links to resolve is what largely inspired me to write Link Bubble.

Thanks a lot. I went through a few iterations on that, and I'm pleased with the final result.

Yup I'll definitely use ABS when I backport it.

Tablet support is definitely coming. I've been inundated with request for a few things I didn't see coming, so as soon as I clear those items out I will get straight on to tablet support.

Hopefully my Nexus7 will have arrived by then..

VolScroll is an additional means of scrolling. Touch scrolling naturally works as you would expect.

I use it primarily when I'm tweetin' & eatin'. One hand is using a fork, the other is holding the phone and easily navigating the feed.

Thanks a lot for the feedback. Once I add a few more core features and implement tablet support, I will backport it to Android 2.x.

Yes: http://techcrunch.com/2010/12/20/aol-acquires-personal-profi...