Feeds

WAC wiki creates Waikiki

It asks developers to comment on draft APIs

Providing a secure and efficient Helpdesk

The Wireless Application Community has published draft specifications for WAC widgets, and is seeking comment from the developer community it so desperately needs to attract.

The specifications are very clearly marked as being draft, with dire warnings against building phones based on the spec, but the idea of the Waikiki is that developers or other interested parties can publicly comment on the proposed API controlling everything from camera and orientation sensors to the widget lifestyle itself.

In WAC terminology, a widget is an application that happens to have been developed using AJAX technologies, so the APIs are JavaScript-based. The WAC will sign widgets that need access to local resources, and distribute them through a warehousing model - local mobile operators run app stores stocked from the WAC warehouse, with anyone else welcome to join the party.

It's a perfectly reasonable model, though few people have leapt to join up just yet. The WAC is backed by the mobile operators, notably Vodafone and China Mobile - the world's largest by revenue and subscribers respectively, but also by a host of others who see the WAC as their last, best, hope of wresting back some control (and associated revenue) from Apple and Google.

The biggest problem facing the WAC will be trying to get the different operators to agree on anything, and within a decent time-scale. Mobile operators are terribly conservative, and gathering them together tends to emphasise that.

Samsung has expressed support, claiming that the WAC complements its Bada platform - but Samsung will declare undying love for anyone with a chequebook. Bada applications will compete directly with WAC widgets, assuming the former lasts long enough for the latter to get established.

WAC needs network operators to put pressure on handset manufacturers to include a WAC client, but before that can happen, someone needs to write a WAC client for the more-popular mobile OSs, which can't happen until the specifications have been nailed down - which is where we come in. ®

Security for virtualized datacentres

More from The Register

next story
TEEN RAMPAGE: Kids in iPhone 6 'Will it bend' YouTube 'prank'
iPhones bent in Norwich? As if the place wasn't weird enough
Consumers agree to give up first-born child for free Wi-Fi – survey
This Herod network's ace – but crap reception in bullrushes
Crouching tiger, FAST ASLEEP dragon: Smugglers can't shift iPhone 6s
China's grey market reports 'sluggish' sales of Apple mobe
Sea-Me-We 5 construction starts
New sub cable to go live 2016
New EU digi-commish struggles with concepts of net neutrality
Oettinger all about the infrastructure – but not big on substance
PEAK IPV4? Global IPv6 traffic is growing, DDoS dying, says Akamai
First time the cache network has seen drop in use of 32-bit-wide IP addresses
EE coughs to BROKEN data usage metrics BLUNDER that short-changes customers
Carrier apologises for 'inflated' measurements cockup
Comcast: Help, help, FCC. Netflix and pals are EXTORTIONISTS
The others guys are being mean so therefore ... monopoly all good, yeah?
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.