Zembly can also be used as a VAS (Value Added Services) platform for a mobile operator.
In its own words...
Zembly lets you collaborate with your friends for developing social apps. Its also a social networking platform.
Zembly basics are here.
Zembly is based on open source project called socialsite.
Zembly has a design time and a runtime component The design time component is basically a light weight browser based IDE (Integrated Development Environment). It is implemented using a Java Applet and supports syntax highlighing.
The runtime, constitutes of browser based client, having a HTML, Java Script and a CSS. While the server side consists of web service created by the developer. The server side web services are basically the business logic, mostly services mashups, created through scripting.
Thus the server side web services can be consumed by not only the default Zembly widgets, but also other clients like JavaME, Brew, ODP (On Device Portal), JavaFX or any other thick clients like .NET.
But, then a mobile operator should strive to be Destination and not a Gateway.
Zembly As SDP (Service Delivery Platform)Zembly lives in cloud, presently it is purely on Internet, that is, Public Cloud. However, by virtue of its open source nature, it can also be deployed inside a telecom network, that is a private cloud. Merging the two platform can create a VAS (Value Added Service) platform; Thus creating a hybrid cloud.
At the basic level, any SDP must support SMS based integration, since SMS or Text Messaging is the most valuable service after voice.
Zembly SMSC (Short Messaging Service Center) IntegrationMM7 (Multimedia Messaging version 7) is a HTTP SOAP based protocol for SMSC integration defined by 3GPP TS 23.140.
Thus MM7 is used for integration of external services with SMSC. However, if an operator lacks a MM7