Samsung Placedge SDK and Resources

Samsung Placedge

Samsung will launch its beacon platform to developers tomorrow. And while the headline is that they’ll be offering a way to let brands use a shared app/beacon registry to reach consumers and thus not even necessarily NEED their own app, they’re also releasing tools for developers.

This move also suggests that the biggest competitor to Samsung for this service isn’t Apple – it’s companies like Gimbal, a spin-off of Qualcomm which offers similar cloud-based services for registering beacons, setting geofences and pushing messages.

The Samsung web site provides more information.

(Their site also looks like it was designed over a few hours in the back of a coffee shop somewhere. Not exactly a polished performance – and has a feeling of being rapidly put together without the help of, you know, a Web designer).

The information about the SDK also indicates that Samsung is, finally, opening up the ability for your Android phone to BE a beacon:

Placedge uses Bluetooth (BT) to send and transmit micro-location data to Samsung smart devices. Bluetooth technology consists two different modes – Central and Peripheral. A device in central mode scans and searches for beacon advertisements, while a device in peripheral mode transmits advertisements to other devices. Currently, Android provides built-in support for central mode BLE only. Samsung Placedge SDK allows Samsung devices to utilize peripheral mode as well.

The site also clarifies that Samsung WILL be supporting a specific requirement for the beacons that the phone can interact with. It’s one of several conditions for using the service, which Samsung outlines:

  • Please note that the Beacon Discovery module discovers beacons that are registered with the Placedge Web Console. Thus, partners need to register beacons in Placedge Server using either the Placedge Web Console or Placedge Server API before scanning for partner beacons using the Placedge SDK.
  • Additionally, Placedge SDK discovers only those beacons that are compliant with Samsung’s Placedge Beacon Specification.
  • Access to the Placedge Web Console and Placedge SDK are limited to registered partners only.

These conditions, and the ability to bypass apps and send messages directly to consumers indicates that Samsung wants to have its cake and eat it too: bypass the app layer, but provide tools to app developers.

Share Your Thoughts

Join our e-mail list for more on iBeacons and BLE. Join the conversation on Twitter, or connect with me on LinkedIn.

What do you think? Can Samsung match the kinds of beacon development tools already on the market?

3 Responses to “Samsung Placedge SDK and Resources”

  1. Hi –
    Hmmm . It’s going to be interesting to see how this pans out. It does provide some insight into their direction. I see what you mean about the site. At least the menu slides out :) – Seems a bit restrictive and I’ve got to compare it with our platform : to see where this stacks up.

  2. Jeff Hest

    This sounds very half-baked (and not just the lousy web site). Who is going to install Samsung beacons in their stores that talk only to Samsung devices enabled for this? We heard this won’t be even out until the Galaxy 6 ships sometime next year and will only work on those devices and later. Not that compelling…

  3. It´s a little bit frustrating to see how, as usual, the war of the “granders” its hitting the developers. In this case, there is hardware in the middle… not so easy to release a new built or version….in function of the caprices of the big companies. If this tech is going to be phone manufacturer dependent…it will dead before born…


Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>