EcranMobile.fr : l'actualité du marketing mobile

Symbian^4 means bad news for developers, amazing news for users




Well, at least the significance of the Symbian Duck’s giant robotic feet is clear now — they’re going to walk all over developers! Oh come on. We kid… We kid… Truth be told, there’s no one as happy as we are to learn that Symbian^4 will finally break app compatibility. This obvious-turned-revelatory tidbit was covered [...]

Well, at least the significance of the Symbian Duck’s giant robotic feet is clear now — they’re going to walk all over developers! Oh come on. We kid… We kid… Truth be told, there’s no one as happy as we are to learn that Symbian^4 will finally break app compatibility. This obvious-turned-revelatory tidbit was covered in a recent interview with Symbian Foundation Catalyst and Futurist David Wood where he discusses the death of Avkon and the birth of Qt where UI elements are concerned. While we’re insanely pro-developer here at BGR, we must be clear in stating that this is awesome, awesome news. Why? Because it confirms what we already knew and what we’ve been dreaming about for what seems like an eternity — Symbian will actually find itself wrapped in a (hopefully) fresh new UI sometime in the not-so-distant future. Think late 2010ish/early 2011ish where consumers are concerned. As for what this means to developers, yes there will be some work involved in order to update the current crop of apps. That is most definitely not a bad thing, however. Come on guys, S60 3rd launched in what, 1924? We’ve been compatible for long enough. It’s time to freshen things up a bit and get rid of that stagnant look that should have been updated long ago. If that means a little more work for devs, we hope they embrace it with open arms.

[Via Engadget Mobile]

Read



Source : http://feedproxy.google.com/~r/TheBoyGeniusReport/...


Jeudi 6 Août 2009


Veille Twitter | Communiqués | Web Review


Recherche Archives


Newsletter Email / RCS

Inscrivez-vous à notre newsletter pour suivre nos actualités.

Le champ SMS doit contenir entre 6 et 19 chiffres et inclure le code pays sans utiliser +/0 (ex. : 33xxxxxxxxx pour la France)
?

Nous utilisons Brevo en tant que plateforme marketing. En soumettant ce formulaire, vous acceptez que les données personnelles que vous avez fournies soient transférées à Brevo pour être traitées conformément à la politique de confidentialité de Brevo.

Terminé