All About Symbian - Symbian, Nokia and S60 unwrapped.
AAS Insight 96 - 6700 Slide, Spotify and Q and A
Published by Rafe Blandford at 13:04 UTC, November 25th 2009
In All About Symbian Insight 96 (AAS Podcast 160), we discuss recent rumour around Nseries in 2012 and the related Symbian / Maemo debate. Then there's news coverage of the Nokia 6700 Slide and Spotify on Symbian. We finish with a number of reader questions ranging from the web as a platform to buggy firmware and augmented reality. You can listen to AAS Insight 96 here or, if you wish to subscribe, here's the RSS feed.
In this podcast we cover:
- Nseries 2012 - Symbian / Maemo rumours
- Nokia 6700 Slide - 160 EUR mid tier phone.
- Spotify on Symbian
- Listener Q and A:
- How can manufacturers release devices with buggy firmware?
- Related to Chrome OS - do we really need apps once the web is good enough?
- What will it take ot get Augmented Reality on Symbian?
News Discussion
Unscrolled
You mean, the new 6700 slide, right?
svdwal
Regarding the Symbian versus Maemo "controversy", at some point Rafe mentioned that both Maemo and Symbian will have Qt to hide most differences between the two OS'es.
This is true, but only if both Maemo and Symbian will standardize on a single UI layer. If they do this then the same UI source code will compile for both OS'es, and the differences in the two OS'es will be hidden behind Qt for most apps.
But if either Symbian or Maemo decides to create different UI layers, then that compatibility is out of the window, and Maemo and Symbian will be come as different as S60 and UIQ are. As of this moment I don't believe a choice has been made to keep Symbian and Maemo compatible at the UI source level.
Technically, both S60 and UIQ are build on Uikon, but that did not prevent the two UI's to become more and more different as time passed.
This is true, but only if both Maemo and Symbian will standardize on a single UI layer. If they do this then the same UI source code will compile for both OS'es, and the differences in the two OS'es will be hidden behind Qt for most apps.
But if either Symbian or Maemo decides to create different UI layers, then that compatibility is out of the window, and Maemo and Symbian will be come as different as S60 and UIQ are. As of this moment I don't believe a choice has been made to keep Symbian and Maemo compatible at the UI source level.
Technically, both S60 and UIQ are build on Uikon, but that did not prevent the two UI's to become more and more different as time passed.
garbleart
re: Dodgy handsets. Despite Ewan's observations about the pressures of getting a phone to mark this should not be used as an excuse. Its is possible to put more resources into regression testing the software on the phone and get a better quality of final product before launch. A company as rich as cash rich as Nokia with its resources should not be relying on comsumers to do their testing for them.
garbleart
Ah yes VT-52 terminals, thats bought back memories! I loved programming in VAX Assembly Language soooo high level, compared to 6502 anyway...
Unregistered
the podcast just finishes i think end is chopped off, it stops while ewan discusses chrome os, it never gets to augmented reality question
stuclark
To counter Steve's argument for delaying handsets: The second a manufacturer delays a handset (such as Samsung did with the i8910), *some* reviewers give that manufacturer / handset endlessly bad press for simply being delayed!
morpheus2702
I just don't understand why manufacturers announce new handsets so far in advance of launch, especially if there is still some way to go in finishing the firmware/hardware.
Take the new crop of Motorola Android handsets - how much time was there between announcement and launch? HTC too don't announce so far out.
I can understand by getting word out there early manufacturers may wish to not lose potential sales from consumers that are ready to buy now but are ready to wait for the new handset. But if after a 6 month wait and the phone is a turkey, the consumer gets the double whammy of 'I waited' and 'this phone is s***!'
I work in consumer electronics and only when the product is ready and on the water do we announce it.
Take the new crop of Motorola Android handsets - how much time was there between announcement and launch? HTC too don't announce so far out.
I can understand by getting word out there early manufacturers may wish to not lose potential sales from consumers that are ready to buy now but are ready to wait for the new handset. But if after a 6 month wait and the phone is a turkey, the consumer gets the double whammy of 'I waited' and 'this phone is s***!'
I work in consumer electronics and only when the product is ready and on the water do we announce it.
Search
Navigation
Social
Advert