According to SevenClick team, this new version will be compatible with all devices based on iOS (iPhone, iPad and iPod), facilitating high security voice calls and data sharing.
This way, we complete the list of Zuppex supported platforms (Android, Blackberry and Windows Mobile).

• Secure voice calls
• Push mail
• Geolocalized contacts
• Calendar
• IM
• Tasks
• Certified notices
• Electronic document signature

Daniel Vecino, TBSgroup SevenClick’s CEO said that this new version comes after the confirmation of multi-tasking capability of the new iPhone, and in response to the demand made by the international market, especially by public administration, secure forces and intelligence agencies.

Vecino also emphasized the business case of Zaragoza City Council, wich has already used Zuppex during the last two years for certified notices sending, and the imminent deployment in Diputación de Teruel and their City Councils. Thus, Teruel Deputies will be the first ones to sign documents with digital signature from a mobile device.

The wait is over!!! Zuppex is here!!!

After a long time of hard working and great expectations, SevenClick is proud to present its brand new product: zuppex.

The first question that will come to your mind is: What is zuppex?

For a more detailled explanation, visit www.zuppex.com, where you can find information about zuppex and and its product suite.

We are very happy and  proud  of this product that, in a short period of time, will change our conception of mobile security and mobile push communication.

Finally, I’d like to thank SevenClick’s zuppex team for their hard work during the last months. A product like this can only be created with enthusiasm and hard work. Congratulations!!!

Link Zuppex web site

Some days ago we talked about the release of the first beta of Android, named ‘Android SDK 0.9 beta’.

Along with some new features and the release itself, we pointed out the bad news of Google dropping of two important APIs: Bluetooth and GTalkService. For sure, more other people has felt disappointed by this, and Google Android’s team has tried to explain their reasons in a post.

The explanation seems to be reasonable: scheduling issues. In fact, they promise next releases will include these APIs, emphasizing bluetooth one. Anyway, it’s hard to believe that Google, with thousands of developers, has not reached to release a proper Bluetooth API in time.

In turn, I think GTalkService – formerly XMPPService – API has suffered other kind of issues. I suspect that Apple’s upcoming push/event notification service – which Jobs said to be ready in September – has made Android’s push platform to be rethinked. Unfortunately.

Link AndroidDevelopersBlog

No, I’m not talking about Alice Cooper’s hit. This article refers to Google’s behaviour regarding Android and Standards. More concretely, about the fact of XMPP being banished from Android in favor of Google’s own protocol for Instant Messaging.

In order to put you in context, please, read the following lines:

“The com.google.android.xmppService package has been replaced by the com.google.android.gtalkservice package. This was done to better reflect the fact that this is a Google-specific service, and not part of the Android core.

This service has two goals: to provide a convenient way for developers to send peer-to-peer messages from their applications between handsets, and to provide an API for sending and receiving instant messages from Google’s Talk servers. Since it is not intended to be a generic XMPP API or gateway, and since in the future it will likely move to a binary protocol that will not be compatible with XMPP, we have renamed the Service to avoid confusion.

Developers who need standards-compliant XMPP functionality are encouraged to use a third-party library that provides that functionality.”

I’ve taken this lines from the Android SDK Milestone 5 Release – API Changes overview information. It’s not secret that Google has lately abandon their late “Don’t be evil” slogan for a more commercial one. But it’s old slogan was more than commercial: it reflected Google behaviour in terms of standards usage and support.

Android is a brand-new Java mobile flavor, not compatible with standard J2ME in any way. This means one thing: fragmentation in the Java Platform. And now, Google removes XMPP, the de-facto standard in internet instant-messaging and presence services, for their own Google Talk service. Google suggest ussing and external API in order to obtain such functionality. But, taking into account that Google is designing ANDROID as an open Mobile Operating System, What’s the point in substituting XMPP for a single purpose- single service protocol like Google Talk? Why don’t keep both options?

In my opinion, Google movement is clearly directed to encourage their own services’ usage in opposition to a more standards based approach. This strategy is not well received by the development community, which bet on open standards, and it will hamper wide adoption of instant messaging services in ANDROID applications.

Bad news for mobile developers. Very bad news.

Link ANDROID SDK Milestone 5