Hacker News new | past | comments | ask | show | jobs | submit login

This is a bug in the app, I don't see how it is Android's fault.

This is a Play Store curation failure _as well as_ a bug in the app.

This sort of fault shouldn't have been allowed to pass.

It's funny how the chrome store has skewed so far the opposite direction (kicking out extensions that claim they need http://*), but any Android app can claim they're a http:// handler.

well it is a pretty transparent use case : the app declares it can respond to any http intent.

The user has to agree to use that app to open http links.

Sure Google could kick this dev butt and ask them to use a more focused intent filter but that's way less of an issue than an extension siphoning all your web browsing.

The Play Store is a disasterous shit show; I don't trust apps on it at all.

tl;dr: what bug, or even what kind of bug?

"The app" does not provide the share intent panel functionality, the framework does, and even if there was some way in which an app could be thought to be to blame, with what permission would it be inserting its resources in a particular spot in the panel?

The app declared itself to be a web browser so the OS asked the user if they wanted to use this new browser.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact