28
Oct
2013-10-28_12-07-03

When a tech company holds a conference for developers, you can pretty much bet the speakers will have something new to share with the attendees. At the very first Samsung Developer Conference, this pattern continues as 5 new and updated SDKs have been announced for the company's various platforms. This batch of SDKs are centered on Android, Smart TVs, and enterprise development.

  • Samsung Smart TV SDK
  • Samsung Multiscreen SDK
  • Samsung Multiscreen Gaming SDK
  • Samsung KNOX SDK
  • Samsung Mobile SDK

2013-10-28_12-38-26

The Mobile SDK is technically new, but it's really meant to bring together various TouchWiz SDKs that had previously been distributed separately. The package now includes: Chord, Gesture, Image Filter, Look, Media Control, Motion, MultiWindow, Pen, Professional Audio, and Visual View.

There is a new Smart TV SDK and two new cross-platform MultiScreen SDKs, one dedicated to regular apps for entertainment and another built in collaboration with Unity to deliver a high quality gaming experience. Details are still a bit sparse, but the session descriptions mention APIs for Android, iOS, and Javascript to interact with Samsung SmartTVs. There are also references to an upcoming product release in February, no doubt for SmartTVs running WebEngine 2014.

Samsung is, unsurprisingly, making a strong push for developers to leverage its newly minted KNOX security layer within the business landscape. The KNOX SDK introduces support for the BYOD (bring your own device) movement and gives developers access to some of the enhanced security features.

Samsung is labeling all of the new SDKs as beta at this time. If you're interested in the Mobile SDK, it is available here. The other SDKs haven't been posted to the developer portal yet, but they will probably turn up in the next few days.

Source: Samsung Tomorrow

Cody Toombs
Cody is a Software Engineer and Writer with a mildly overwhelming obsession with smartphones and the mobile world. If he’s been pulled away from the computer for any length of time, you might find him talking about cocktails and movies, sometimes resulting in the consumption of both.

  • Albert H

    Wow, Samsung's APIs are interesting... a mix of Java, Javascript, and Python. Actually, not even Java is included - it's all just Javascript and Python. And those code highlighting colors are known to steal even the best developers' eyes. Freaky APIs and colors just in time for Halloween? You bet!

    Kidding aside, I took a peek at Samsung's Mobile SDK, and one thing (and probably the only thing) that caught my eye was the "Professional Audio" SDK. Curious as to how serious they are about it, I opened the overview page... and it looks like they are using JACK Audio for their API. JACK Audio is an audio server from Linux, known to be well suited for professional audio. For these guys, they're aiming at the iOS guys who hook up iPads to do mixing and such. They're actually serious... good for them for stepping up.

    • Michael Pahl

      0 latency then?

      • Albert H

        Yup. http://jackaudio.org/no_extra_latency

        Of course, actual latency depends on the hardware, kernel and surrounding user-space software. They probably aren't using a realtime kernel because that would significantly slow down their devices, but their overview hints that they do try to raise the task priority when the API is used, leading to lower latency.

        Nevertheless, JACK Audio interfaces the kernel level sound APIs (ALSA), not Android's sound APIs, so we're still looking at much lower latencies than what Android's sound system can offer.

        • Adrian Meredith

          except for the latency doesn't come from android, its the actual drivers/hardware themselves. The latest version of android already has a fast path high priority audio stream that works directly through opensl.

  • Adrian Meredith

    I hope developers stay well away from these proprietary apis. It wont benefit anyone

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      I can't entirely agree with that. It really depends on the circumstances. For example, there really aren't any competitors putting out products with a stylus comparable to the S-Pen, and there are a lot of great ways to build on it. Until some kind of universal API exists, it would be a shame for developers to ignore the potential.

      On the other hand, stuff like the Multiscreen Gaming SDK and Chord seem like traps to get developers to rely on proprietary libraries for things that obviously could have been done in a less platform dependent way.

  • beatles

    CrapSung aim is to develop more crapiness into LagWiz

Quantcast