Can we create an app that will receive push notification from a server, like in Phones and Glass
Since we have WiFi enabled Watches available now, we can connect to internet, but does it support push from external entity(Server)?
That is not possible AFIK.
You need to push the message to the phone and forward the message via the Data API. You need to keep in mind that the WiFi connection is only a fallback when the bluetooth connection is not available.
You can do it now from Android Wear 2.0 Developer Preview. Android can wear can directly make own network calls and same old FCM/GCM will work.
Under Network Access and Cloud Messaging
Android Wear apps can make their own network requests. When a watch has a Bluetooth connection to a phone, the watch's network traffic is proxied through the phone. When a phone is unavailable, Wi-Fi and cellular networks are used, depending on the hardware. The Wear platform handles transitions between networks. A watch's network access thus does not require the Wearable Data Layer API.
For sending notifications, apps can directly use Firebase Cloud Messaging (FCM), which replaces Google Cloud Messaging, or continue to use GCM.
No APIs for network access or FCM are specific to Android Wear. Refer to the existing documentation about connecting to a network and cloud messaging.
More details - https://developer.android.com/wear/preview/features/standalone-apps.html#network_access
Related
Basically how do I initialize the flow so a use can login to their desktop from their mobile phone?
Any help or advice in pointing to their docs for the right flow. https://developer.transmitsecurity.com/sdk-ref/webauthn/interfaces/webauthnsdk/
CTAP2 allows apps on mobile phones to act as roaming authenticators. An app may implement the protocol over one or more of the supported transports.
However, there are use cases where the web or native app being accessed would be run on the same mobile device as the roaming authenticator. Can this use case be supported by CTAP2?
PS: Why is there no ctap or ctap2 tag? I used 'fido' as a proxy.
However, there are use cases where the web or native app being accessed would be run on the same mobile device as the roaming authenticator. Can this use case be supported by CTAP2?
CTAP defines a protocol that is used between devices. For apps to provide credentials on the same device, the OS of that device would need to support them plugging into the standard APIs.
We (Google) said yesterday, “Please stay tuned for more updates from us in the next year as we introduce changes to Android, enabling third party credential managers to support passkeys for their users.” But I believe that's the most that any of the platforms have said on this point so far.
Is there any way to enable/disable the microphone on Sonos One (2. Gen) via API calls? E.g. on the openhab binding for sonos I can track the state of the microphone, but can't change it. However when adding any voice assistant the microphone is turned on automatically at the Sonos One so it is possible via software, right?
Microphone access is very limited indeed due to privacy concerns. I am not aware of any way of accessing it directly.
I'm working on react native push notifications. i'm looking for some answers before i make a purchase to any third party notification provider
Why do third party notifications providers such as OneSignal, Pusher & PubNub are based on Firebase Cloud Messaging?
Can't they send notifications independently without relying on Firebase. why pay more to third party providers when FCM does the work for free?
Firebase is a Brand of Services
First, Firebase is a brand that encompasses more than just 1 thing. For example, there is Firebase the realtime database, and there is FCM (Firebase Cloud Messaging) which is the current incarnation of GCM (Google Cloud Messaging) which came from the original product, C2DM (Cloud to Device Messaging).
PubNub and others are push gateway providers
Second, third party realtime messaging services are not push notification services, rather they offer push notification gateways to the push services: APNS for iOS and FCM for Android.
PubNub Realtime Messaging & Mobile Push Notifications
In PubNub's case (my employer), we provide a realtime messaging service (publish, subscribe and much more) and if you provide a valid APNS and/or FCM payload, we will not only deliver that realtime message to active subscribers, we will also send a mobile push notification to the devices that are properly registered for them on that channel you published the message to. This allows the message to be delivered when the app on the device is either not active (background) or not running and therefore, no active connection to PubNub unless it is running in a background service). Now you can have an active connection to PubNub in the background with proper implementation and permissions from the owner of the device (easier on Android than on iOS which also has a review process that rejects apps that don't qualify as valid background service apps).
For Your Consideration
If you did not use a service such as PubNub or one of the other realtime messaging vendors or a push notification specific service like Urban Airship, you would have to implement your own server-based push notification service which is possible but might be more work than you would expect especially if it needs to scale, be secure, robust, etc.
The real question you should ask is do you need realtime messaging in your app or just push notifications and to what level of scalability where it is worth paying a third party for all that goodness.
I need to use Webrtc api for video and audio call between two users.Actually i have a Elearning learning management system with many users recently i have developed a chat system so that users logged in LMS can chat each other using simple php,ajax and jquery.Now i have implemented only text chat.
I need to develop video chat also like Google hangout and facebook video chat.Users registered in my system are having different email domains means some one have gmail account ,yahoo account etc.
Expecting quick reply
Thanks
To get started with WebRTC, I would suggest to first have a look at the following tutorial on WebRTC fundamentals.
You can then start to implement the native WebRTC API but be aware that you won’t be able to establish a video call if you don’t add a signaling server which does not come built-in with the WebRTC API.
Also if the caller and callee are connected to two different networks, you’ll often need ICE, STUN and TURN servers. Video chat is more complex to implement than text chat and if you don’t have the time and the resources to learn the fundamentals and deploy servers, I would suggest you give a try to a WebRTC Platform that already have an up and running cloud infrastructure to which you can access through an API.
It is the type of WebRTC Platform that we offer at Weemo.