I understand Parse provides translation of its own api and native APIs. Do anybody know if it also supports the native APIs for peripheral access, such as bluetooth, etc? Thanks.
It does not. Parse only provide APIs to access their services (Data, CloudCode, Push, Analytics, etc) and Social Login through Facebook or Twitter.
Related
I would like to send a BLE Eddystone beacon from a web page. My application requires to send SSID info to a BLE listener. My thought is to have a user load a URL on a smartphone that would run JS to send periodic BLE Eddystone-UID beacons with SSID info embedded. I need the web page to work on both Android and iOS phones. Is there a simple way to do this using Javascript?
I looked into physical web but it did not seem to provide this capability.
thanks,
Ian
The current version of the Web Bluetooth API specification allows websites, running in the Central role, to connect to remote GATT Servers over a BLE connection. What you're looking for is a way to run in the Server role to advertise your data.
In your case, I'd recommend you have a look at https://www.npmjs.com/package/#abandonware/bleno
When we use Google Apps Script to call the Google/YouTube API (such as YouTube API, YouTube Content ID API etc), 3 legged oAuth authentication approach, sometimes we got the message "backend error". If we tried again, the same call would be successful. The backend error rate sometimes is pretty high.
We also used (we also could use) Google Cloud Client Library and service account to call Google/YouTube API, 2 legged oAuth authentication approach to make the same API call.
Due to Google encourages us to use newer Cloud Client Library if we can ,instead of the older API library, I am wondering will the backend error rate going down if we use the Google cloud client library calling the Google API instead.
Or backend error is purely on Google Backend, it does not matter which library we use to call the API?
Thanks!
Google Cloud's Client Libraries can give you some performance benefits by using gRPC. This is because gRPC-enabled API clients use protocol buffers and gRPC over HTTP2 to talk to the RPC interface.
Protocol buffers are smaller and faster than using JSON over HTTP to the REST interface. So, in a way, they're better for everyone and can provide lots of benefits in terms of throughput and CPU usage.
But, if there's a fail after the backend's RPC interface, then there is no difference.
Also note that they could provide an exponential backoff strategy to handle errors and retries.
There's a way from Codename One to provide access to Near Field Communication (NFC) ?
Anything new, out this post codename-one-nfc-beacon?
NFC is an Android only API and even there the availability in devices is "problematic". In iOS it's restricted to payment so there is no access to the underlying hardware. So there is no point in supporting the API in a framework that is designed for cross platform. I'm sure you can create a cn1lib similar to the fingerprint reader API or the SMS intercept API.
Hi I want to create an app using google nearby message api. I want it to be completely offline.
Is it possible? Does google needs internet connection for using this Nearby api?
I know it uses bluetooth and WIFI things to share the data!
I want to know whether it needs internet connection at its initial stage? since it needs to retrieve some token from the cloud.
Help me in this!
Thanks in advance!
Yes, Nearby Messages requires devices to have internet access. Discovery is accomplished via BLE (Bluetooth Low Energy), WiFi, and audio (using near-ultrasonic frequencies), but the cloud is needed for message delivery after discovery. Nearby doesn't yet provide a pure peer-to-peer solution.
Hi i am developing windows mobile application for dopod 818 pro to send / receive sms.
is it possible to access sms functionality via j2me?
You can not read SMS from Inbox directly. For reading SMS from Inbox you need APIBridge.jar. APIBridge is an extensible mechanism to access device features in WRT, Flash Lite, and Java applications.
You can use APIBridge in two ways. APIBridge can be used as it is shipped, to access features of Symbian using the plug-ins provided. However, because APIBridge is based on a plug-in architecture, you can also use it to offer new features by creating plug-ins that access functions of Symbian or your own native Symbian applications.
Please note that APIBridge.jar works for Symbian OS Based Phone Only. Not for S40 Device.