-
Notifications
You must be signed in to change notification settings - Fork 38
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
Adding "Android" as install method, along with Chrome/Firefox/Edge #446
Comments
When coding this, we should also keep in mind that Edge is currently (in Canary) testing allowing us to install any extension, so it should be possible for this to easily include support for Edge if they allow it in the future. |
If Edge for Android allows Chrome Web Store downloads, then we should prefer that over the Edge store. The Kiwi detection logic could be reused in that case, most likely, as it's another Chromium fork. |
The current alpha requires manually inputting the Edge webstore ID, so it remains to be seen how this will play out. Either way, we should have plenty of notice for new changes so I'm just putting it on the radar for now. |
I'm not entirely convinced for two reasons.
|
Is that the case, though? Most people currently might not expect it to work, but plenty of people will try or learn about this without understanding how it works from a technical perspective.
Fair. We could include a pop-up when clicking the button (and even maybe upon installing the extension) that we don't prioritize support for mobile browsers. Either way, it could be helpful to people on tablets or Chromebooks who may have access to mice/trackpads. |
We do, multiple people were using Firefox for Android and we only came to notice as v1.38.0 completely broke the extension for it. And we fixed it through a dedicated update even though it's not "officially" supported. |
Also, we can remove the Android button later if we want. We're not forced to keep it forever. It's well known that Google does not like extension support on mobile due to adblockers. Of course some of our users won't know how (or if) they can install extensions on mobile. It's by design. |
+1 from feedback:
|
+1 from feedback (reading messages from last month with delay):
|
@DNin01 Have you read this issue? It's related to touch screens I guess this is 'help wanted' |
I don't know what to do here. Mobile Firefox and Edge combined have a little less than 1% of the market share right now1, and I don't know how Kiwi compares. If you want to answer mobile browser support, I would mention Firefox, Edge and Kiwi all as options, while noting that we don't officially support mobile browsers. My next idea would be to leave it to the users to figure out how to install a browser extension on the platform they are using. Footnotes |
Surely that number grows if you exclude people that don't use any extensions on desktop either. (probably majority of the human population)
Sure, but in my opinion it's not sufficient to include this in the FAQs. We still get ocasional feedback about installing in mobile devices and tablets.
I think that is a terrible idea because users don't typically install extensions on mobile, but Scratch Addons may be the first one they do install if we tell them how. |
See my comment here. Quoting it:
Since then, our FAQ has been updated accordingly, it suggests Firefox over Kiwi.
I now suggest that our install logic detects Android and that we add an "Android" button in the install section of the homepage. It would focus on both Android phones and Android tablets.
What do you think?
The text was updated successfully, but these errors were encountered: