Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow users to select their default action handler #52

Open
PaulKinlan opened this issue Jul 7, 2011 · 3 comments
Open

Allow users to select their default action handler #52

PaulKinlan opened this issue Jul 7, 2011 · 3 comments

Comments

@PaulKinlan
Copy link
Owner

It would be great if a user could "star" a preferred handler so that they don't keep getting prompted to select an app.

PaulKinlan added a commit that referenced this issue Jul 15, 2011
PaulKinlan added a commit that referenced this issue Jul 15, 2011
PaulKinlan added a commit that referenced this issue Jul 15, 2011
PaulKinlan added a commit that referenced this issue Jul 15, 2011
PaulKinlan added a commit that referenced this issue Jul 15, 2011
@paddycarver
Copy link

I'm working on an application with a few thousand users (currently) and would love to support Web Intents. But I can't until this issue is resolved-- the extra step my users would have to undertake for the sake of Web Intent integration would alienate too many users. The app works because it's lightweight and quick. I notice this hasn't had anything done with it in a few months; is there a reason why? Is it still coming? Is there anything I can do to help move it along?

@PaulKinlan
Copy link
Owner Author

I removed the default action because the user experience in the shim was actually worse, for instance you can't open a new window without a click, which means that opening the default app in the small picker..... Good news though, this is just a limitation of the shim, it is up to the User Agent to decide how it implements it natively.

What is your app? Why would the extra click alienate users? How would you suggest we work around it?

@paddycarver
Copy link

I'm working on the 2cloud app (http://www.2cloudproject.com) and introducing a web app to complement our Android app. Kind of Chrome to Phone and Phone to Chrome smushed into one, with a couple of twists.

I think part of my problem may be some ignorance about WI. What's the difference between the shim (the JavaScript file) and the User Agent (does this have a special meaning for WI, or is it what I think it is? What UAs support WI right now?)?

The app is going to be accessed a lot of the time through a Chrome extension. I'd like to try and limit the number of Chrome extensions users need to install, so I wanted to support WI and actually send through Web Intents. This would actually help me, because we are an open source project and allow users to host their own instances. This way they could register multiple hosts and choose which to use. It would be a problem, however, for 99% of the users to have to make that extra choice every time they want to send a link. Most wouldn't understand why the window keeps popping up and why they have to click on the only handler available. Just as Android only asks which app should handle an Intent if there is more than one app that CAN handle the intent, I'd like Web Intents to only prompt if there's more than one registered handler.

EDIT: Oops, forgot suggestions for workaround. I guess that would be my suggestion for a workaround. If the user has only one handler registered, don't even open the window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants