Android SDK 0.50.0 – spend less time coding and produce more results

Before this latest version, it was easy to implement Ziggeo into your Android apps. With the latest version however, this is simplified even further and yet you get access to many options you did not before! The `form` that you are using to talk with Ziggeo code in Android SDK now looks and feels just like it does if you are using some other SDK as well. What that means for you is that your developers can now focus more on your code and your functionality, while Ziggeo has a more uniform look and feel. Basically, if you have a developer that implemented Ziggeo for you into your web service and you are looking to create Android App - well the same developer would know exactly which calls would need to be made and why. The only difference is the native app code. This should result in faster development cycles and easy expanding from web to native Android apps. For example, to create video before, you would need to make the following calls: [code language="java"] ziggeo.createVideo(this, maxDuration); [/code] and you would need to subscribe to receive the results: [code language="java"] @Subscribe public void onVideoSent(VideoSentEvent event){} @Subscribe public void onCreateVideoError(CreateVideoErrorEvent event){} [/code] Now you would call it as: [code language="java"] ziggeo.videos().create(HashMap<String, String> argsMap, Callback callback); [/code] As you can see there is no @Subscribe event present. That is because you pass the callback to the function call and that same callback will be called as soon as the response is received from our servers. This means that from where you make the call, you can quickly see where the result calls will be made instead of finding the right subscribe code. Having the videos() 'segment' and callbacks available is great, however you get access to much more: 1. indexing - searching, for example based on tags 2. deleting 3. updating - as web API, you can upgrade details associated with the video 4. retrieving - get video or image to your app As mentioned subscribing to events is now removed as well. Instead of that, you simply provide a callback function that gets called with the results of the call, which means more control over what and how you want to happen.

Introducing Streams

Do you want to be able to access and use streams from your Android app? Now that is possible as well. [code language="java"] //create streams ziggeo.streams().create(String videoTokenOrKey, Callback callback); //attach image to stream ziggeo.streams().attachImage(videoTokenOrKey, String streamTokenOrKey, File imageFile, Callback callback); //attach video to stream ziggeo.streams().attachVideo(String videoTokenOrKey, String streamTokenOrKey, File videoFile, Callback callback); //Bind the video and image and submit the stream ziggeo.streams().bind(String videoTokenOrKey, String streamTokenOrKey, Callback callback); //retrieve stream ziggeo.streams().get(String videoTokenOrKey, String streamTokenOrKey, Callback callback); //delete stream ziggeo.streams().delete(String videoTokenOrKey, String streamTokenOrKey, Callback callback); [/code] As you can see calls are made simple and intuitive just like our web API is and just like videos, streams also have callback parameters to allow you to handle results as you want them. We do suggest checking out the Android SDK readme file for more details in regards to the same: https://github.com/Ziggeo/Android-Client-SDK Of course, if you have any questions, feel free to contact our friendly support team.