I am working on Gimbal Beacons. I have registered my gimbal beacon on Google Beacon DashBoard. Now I can receive notification on any android device using my gimbal beacon. Now I want to do the same thing for iPhones. So that when an iPhone user opens bluetooth in beacon's range then a notification is received on iPhone. Please help me..!
Apple does not have an equivalent of Google's Nearby functionality that allows Android devices with Google Play Services to receive notifications when a beacon is in vicinity without a third party app installed.
On iOS devices, a third part app is generally required to send notifications for nearby beacons. Only one built-in app and one fairly common add-on app allow on iOS respond to third party beacons:
Passbook: if a user has installed a pass associated with a beacon, a notification will be displayed when it is nearby.
Google Chrome: responds to Eddystone-URL beacons if the Chrome Today widget gas been enabled. (Very few iOS users have Chrome and enable this.)
Other than the above, you need a third party app to make iOS respond to beacons.
Related
Can i know is it possible to communicate with Beacon without having any Mobile app on device?
Thanks in advance
Both Android and iOS devices need some kind of app installed to interact with your beacons. Some phones have such apps pre-installed, but the options are limited. The two such apps with the widest distribution are:
Google Chrome App (Android/iOS)
Google's Chrome app will interact with beacons supporting Eddystone-URL (also known as physical web), which transmit a URL that can be displayed within Chrome when the app detects it.
This works on both Android and iOS devices with Chrome installed. For newer Android phones, this is a relatively high percentage of devices. For iOS, it is a very small percentage, as the app is not installed by default. This makes it of very limited use on iOS.
The other real drawback to relying on Chrome for beacon detection is the hoops users have to jump through to opt-in, and the way the beacon notifications are buried. Until users opt-in, they will see no notifications on beacon detections. Once they do, they will see a very generic notification "Physical web beacons are nearby", and only once the user taps on that are the specifics about the web page associated with the beacon transmitted URL displayed.
Passbook (iOS)
Apple's passbook app will bring up a passbook entry (usually used for tickets, coupons, etc.) associated with a set of iBeacon identifiers if the user comes within range of the beacon. In order to use this, however, the user must first download the passbook entry to his or her iPhone. Only once this is downloaded and opened will the app respond to associated beacons.
EDIT April 2020: For a time prior to December 2018 Google supported app-less notifications based on beacon detection using their Google Nearby product. This was discontinued in December 2018 due to predictable abuse and spam that it generated. While you may find some outdated documentation online about this ability, understand that this feature no longer works. As of this writing, my understanding is that this answer is still correct.
You should checkout Eddystones from Google. They can push you URLs even without app.
If you want to interact with beacons and do custom stuff (notifications, http requests, etc) you will need an app.
I am using eddystone beacons to transmit my business url. How can I make the url notification received to alert thru sound on the users device? Any idea?
Understand that Eddystone-URL beacon advertisements don't automatically do anything on a user's phone unless they have an app installed to detect them.
Chrome for iOS and Android (installed on many newer Android devices, but very few iOS devices) will automatically detect Eddystone-URL advertisements and display a notification from Chrome if the user has opted-in. However, no sound is played. Bottom line: on a phone without a custom app, detecting an Eddystone-URL will not cause a sound to play.
If you build a custom app and get it installed on users' devices, you can certainly make it play a sound on Android devices when the beacon is detected. On iOS devices, you could also display a local notification on the device that will play a sound, but only if the user has the volume turned up on the device, does not have do not disturb on, and has opted-in to receiving notifications from the app.
I have been doing lots of research trying to figure out if it is possible to create wear notifications with custom layouts over the past few months, but am struggling to find a solution.
I have tried to implement the following suggestions to no luck:
https://possiblemobile.com/2014/07/create-custom-ongoing-notification-android-wear/
http://android-wear-docs.readthedocs.org/en/latest/sync.html
Custom UI for Android Wear Notifications
Most of what I have read have instructed that in order to do this, I should create an android wear app with a data listener. The idea being the phone would send certain data to the watch (say a string) based on the type of notification it wants to send. I would disable the automatically generated wear notification. In its place, the Android Wear app listener would know what type of notification it is based on the string and display my custom pages for that notification instead.
My first problem I have run into is I have no idea how to debug code like this. Since in Android studio you can only launch the device app or the wear app, but not both at the same time.
The other question I have is, does the Android Wear app run in the background when the Device App is running? Do you have to open the Android Wear App first for the listener to be even working (if so then I guess this is not a solution to custom notifications)?
Is it actually possible to create custom layout android wear notifications?
If you want to use a custom layout for your notifications, you should create the notification on the watch, following Creating Custom Layouts. You can even make the custom notifications clickable, you can add actions that will open activities on the watch, etc.
For that, you can send a message from your phone to your watch and the listener implemented on your watch will receive it and then, create and display the notification using the correct layout corresponding to the message sent, for example.
In this case, the best way is to implement a WearableListenerService on your wearable. Its lifecycle is handled by the system which binds it only when necessary.
To debug, you install the wear app on the wear emulator or your watch, you install the mobile app on your phone and finally you connect the two following this tutorial if you're using the emulator or via bluetooth if you're using a watch (link in the tutorial).
The Android Wear app connects your phone to your watch, whether it is an emulator or not. So, in order for your message to be received, you must have connected wear and mobile via Android Wear. Then, once the connection is established, you don't necessarily need to keep it open. So yes, the Android Wear app runs in background.
2 questions.
Is it possible to send AppleScript actions to an apple watch ?? Like send a string of text to be displayed on an Apple Watch ?
If question one isn't possible is it possible to send information directly from an OS X app to an Apple Watch ?
Not directly. You could send a message to a remote push notification service which the (phone or) watch could receive and display, provided it has registered itself with that service.
Apple Watch takes full advantage of the existing interactive notification support on iOS. If your iOS app supports notifications, Apple Watch displays those notifications at appropriate times. When one of your app’s local or remote notifications arrives on the user’s iPhone, iOS decides whether to display that notification on the iPhone or on the Apple Watch.
Not directly. You couldn't open a connection to the watch from a client on your Mac. You could initiate a connection from your watch or phone to a service, and the service could return a response.
For more information on notifications, see the WatchKit Programming Guide.
In Android Wear it shows the notification and we can reply back through wearable device. But how to start any app from the Wearable device like voice input("Ok Google") or tap on the icon. Action should start from the wearable device not from mobile.
For Example to start my mobile's camera through Android Wear Device i will give voice input as "start Camera" and camera should start.
With the current preview-version of the SDK, this is not possible yet.
But looking at http://developer.android.com/wear/design/user-interface.html tells you, that this will possible using the "Cue Cards".
You can do this now! :)
With the release of the Wear SDK (API Level 20, Android 4.4W), you can now develop Wear applications with very much the same stack as standard Android apps (i.e. Activities, Services, Layouts, Views, &c).
There is also an API for communication, which for example Google Play Music uses to control media playback from the watch.Therefore, you could develop an application, installed both in the Wear device and in the handheld, to launch the phone's camera when started (by sending the command from the Wear activity).