The following anchor tag utilises the SMS URI scheme to open the messenging app on supported mobile browsers:
Send SMS
Does anybody know what mobile browsers are supported, or where I can find a suppport list?
I am most interested to know the earliest versions of ios and chrome for android supporting this.
Related
I don't find how to use Gmail addons inside Inbox:
https://inbox.gmail.com
Is it not supported?
The documentation says:
The contextual cards you create for your add-ons work for both web and mobile
versions of Gmail.
Sidenote: Gmail addons are not supported on mobile version of the website https://mail.google.com, not supported in the iOS Gmail app, seems not supported in Inbox. Are Gmail addons in decline (so not worth spending time developing one) or just in its infancy (that's why it's not supported on all platforms yet)?
Is there any way to make a web page scan for beacons on iOS ? I know that no iOS web browser supports Web Bluetooth at the present. I even could not find any information about if Chrome team is planning to add support for Web Bluetooth for Chrome on iOS.
Is there any other way to scan for the beacons on iOS thru' web browsers (be it Safari or Chrome) ?
Thanks
Unfortunately, Google can't add Web Bluetooth to Chrome for iOS without Apple's participation, and Apple has given no indication that they are supporting the Web Bluetooth project.
Understand that Apple restricts web browsers on iOS to use Safari or Safari web views, which has the same JavaScript engine and bindings as Safari. Google Chrome for iOS is required to use the same internal rendering and JavaScript engine as Safari, which simply does not support Web Bluetooth.
Bottom line: While it is possible that Apple will one day decide to join the Web Bluetooth party, there can be no support on third party iOS browsers until Apple decides to do so.
An external native application should communicate with browser extensions, e.g. send information to browsers what information to fill on web pages.
Those plugins or browser extensions are not yet developed, but I need to support at least Chrome, Firefox and Safari.
What kind of technology can be used to communicate external application with browser extensions? I checked Chrome and it has native messaging for these kind of cases, but I need generic solution what should work for other browsers as well. Any ideas?
There is no generic solution to compatible with all browsers at the moment. So you have to develop different extensions by using different ways for different browsers.
For Safari, you can see here
https://developer.apple.com/library/safari/documentation/Tools/Conceptual/SafariExtensionGuide/CommunicatingwithyourOSXApplication/CommunicatingwithyourOSXApplication.html#//apple_ref/doc/uid/TP40009977-CH23-SW4
But unfortunately, it only supports from Safari 9.0 and OSX 10.10
For Chrome, you already know that Native Messaging is the right choice.
For Firefox, you can create a server socket, and listen to specific port. While your native application communicate with Firefox extension through the port. You can find an example here: TcpSocket listen on Firefox addon
for example, growl flashes a message in the upper right corner regardless of which application is running. Skype makes the icon in the dock have a little red dot with a number of new messages. Is there anyway to write a chrome extension to have this type of functionality? that is, I want to write a chat system that works in the browser but also notifies users when they have closed my site's tab, or even when chrome is not running.
I could write a native client in addition to my browser based client, but that's double the work. (Tripple the work if you bother with a native window's client vs. just OSX but who would do that?)
Chrome can create "Desktop Notifications" See the Documentation
It's also possible to have the notifications visible when chrome is closed providing you create a "background process". this question/answer might point you in the right direction.
Chrome supports the text-only version of the W3C desktop notification standard. Chrome deprecated the HTML version about a year ago and will stop supporting it very soon. Any webpage viewed in Chrome and any Chrome extension can use this API.
The Rich Notifications API is available to Chrome extensions and packaged apps. As of today, it's dev-channel only and is iterating rapidly. It has implementations on ChromeOS and Windows, with Mac on the way. Linux currently delegates to the W3C implementation. The API is not a 1:1 replacement of W3C HTML desktop notifications, but it does provide many layout options for common use cases.
Web browser plug-ins such as Flash already provide VoIP functionality in a web browser, but is it possible to have browser VoIP without any plug-ins?
Ericsson Labs has posted information using the device element to allow for microphone input. This, in addition with WebSockets could be used to implement VoIP. However, the device element is not implemented in any web browser yet.
No there isn't but the device element will likely be the way in the future, as you mentioned. I don't think it will take too long for browsers to look into it however. There are also the WAC APIs, but they are only on mobile, and not shipping quite yet.
Update: There is now a standard in development called WebRTC. Drafts of this spec are supported by Chrome and Firefox. Microsoft have made an alternative proposal called CU-RTC-Web