Windows Phone 7 (p)review: Mango

I’ll preface this “review” by saying the following. This is NOT final code and there will likely be significant changes and additions to both the aesthetics and performance of the Operating System when the final build is released to OEM’s. Further, the hardware improvement likely to accompany this update, in particular the newer 45nm chipsets should improve user experience significantly. The build used for the majority of this review was Build 7661. Comments marked with “update” were reviewed using build 7712 and the final release to manufacturing build is 7720.
The installation process:
Because the update that I’m currently using is more of a mod as opposed to a pre-vetted press device, my experience may be marginally different than other (p)reviewers of Mango. The installation process, in spite of this “mod” was rather straightforward but by no means short. Before updating, the entire contents of my memory card (yes it works in my device) and the ROM were backed up, all 13 gigs of it. While certainly appreciated, it was a painfully long wait for backup followed by a significant wait for the update to install (on the order of 50-70 minutes for both tasks to be completed).
First impressions:
When the device first boots up you’ll be VERY hard pressed to notice any differences between the old version of the OS and the newer version; thankfully all of that changes with a simple swipe to the left.
The first thing you notice is the placement of letters in the applications list these are meant to give users an easier time identifying where in the list they are. Whilst scrolling, it’s important to note that the current letter that you’re in is present at the top of the screen. Also, in the event that you have a ridiculously long list, a simple tap on a letter will bring up a jump-list, allowing you to jump to a specific letter. In addition there’s a new search button added to the mix in the event your number of apps exceeds your tolerance for scrolling.
The live tile area as of right now isn’t being used to the extent that developers both first party and otherwise are expected to be using it come fall this year. However, the tiles that ARE available are significantly more responsive, reliable and update more frequently as well as providing loads more useful glance-and-go information. Hopefully with the added developer back-ends we’ll see many interesting uses of live tiles (although, developers seem to be well ahead on that front).
New additions:
One of Mango’s main selling points is the addition of nearly 500 new features and a great many API’s to allow developers to tap into and deliver these features to the waiting masses (definitely not that many people to be perfectly honest).
Search
First up is the most accessible addition and that relates to search. The three main additions are “Local Scout” which is pretty much a faster and better-integrated version of Lonely Planet found on Ovi Maps; Bing Music which is like Shazam except surprisingly faster (both in load time and in song identification), Image searching (finally!) and Bing Vision which is an integrated version of Google Goggles (can’t wait to put this to good use when I travel to Europe) .
Local Scout:
I’ve been living in the same city for the past 4 years and I still haven’t seen most of the supposedly “good” places nearby. Local scout is broken into 4 main “pivots”:-
· Eat and drink
· See + do
· Shop
· Highlights
Local scout creates a list of 20 items, attractions and/or businesses and arranges them by distance (closest is #1 logically). It also collates ratings, price information and addresses for these places. All of which can be navigated to using the turn-by-turn navigation bundled with the OS- more on that later. Local scout though is certainly a much appreciated addition to the OS and I can see myself using it with increasing regularity, especially while travelling.
Bing Music is pretty much like Shazam, tell it to listen to music and it’ll identify the song then you can be on your merry way.
There are of course hooks that tie into the Zune Music Store, though I can’t imagine many of you actually using it. It does the job and does it well, while managing to stay out of your way. Shazam certainly just lost a few customers.
Image search is pretty much like the images tab on Google searches. Nothing special here but nice to finally see it bundled in AND easily accessible (the same can’t be said of other operating systems).
Bing Vision as mentioned earlier is a lot like Google Goggles. Unlike Goggles it doesn’t inhabit a separate space from the regular search feature and while its success or failure in reading text, bar codes and QR codes is very much dependent on the user and the camera in play, the accessibility of the feature will lead to invariably greater use in the future.
Of course, being an internet-dependent service in the case of translation, Bar code and QR code look-ups it will be interesting to see how this technology and other similar ones improve and develop in the future. Did I mention the translate feature ?
Multitasking:
Another one of the big additions in Mango is multi-tasking. Unfortunately it doesn’t quite work for 3rd Party apps, at least until developers recompile their applications for Windows Phone 7.1 (aka Mango) instead of Windows Phone 7.0. As such, the BEST multitasking experience is limited to built-in applications. That said, all indications point towards minimal work at best on the part of developers which will ensure a good experience for end-users.
The multitasking UI is called up by a long-press on the “back” key. Unlike WebOS and Symbian, Windows Phone only shows the 5 most recent applications used with this UI. This is NOT to say that these are the only apps paused or running in the background etc. but a conscious design choice to avoid mindless scrolling, especially when there’s no MeeGo-esque pinch to zoom gesture to view more running applications.
Strangely enough (and this relates to Microsoft’s regular user first approach) there’s no visible way to control dismiss an application that’s visible in this task switching UI. Applications CAN be closed by pressing back to repeatedly move through the backstack though it is far from an elegant solution. I can only imagine that Microsoft gave little thought to users that might wish to dismiss applications from this view.
Many applications however, are allowed to run certain tasks whilst in the background. Microsoft has thankfully given users the ability to manage how and when applications can run these tasks, albeit the requisite menu is somewhat buried in the device. Nice to see that they still have some consideration for the more tech-savvy among us.
I won’t cover the specifics of Windows Phone’s multitasking implementation here (especially when I’ve covered it here before) but suffice it to say that it should serve most people adequately. That said, power-users who want to read webpages while simultaneously viewing turn by turn navigation directions while also watching a video should probably look elsewhere.
Windows Live aka MSN chat and Facebook chat:
Yes Microsoft recently acquired Skype and that’s all the rage but alas it won’t be making its way to this version of Windows Phone in integrated form. Setting up both Windows Live and Facebook chat is pretty much automatic albeit if you possess multiple hotmail or windows live addresses, only the primary one will work with chat (at the current time at least). Connecting facebook chat requires going to your messenger account on your PC and linking the two before actually utilizing chat. Thankfully the process is barely 3 clicks but it’s still not nearly as smooth a setup as I was expecting. Once done though, chatting with facebook contacts or live contacts is quite a breeze. For better or worse, all threads that are started with your contacts, be they online or offline are housed in the same area.
Threads are grouped together by contact name however, meaning if you have a conversation via text, live or Facebook, you won’t see 3 separate threads in the main threads area. That said, you won’t see online conversations and texts conversations in one chronological thread. Instead they’re kept separated from one another AND there are ever present notifications to indicate which service you’re using at any point in time. I’ve had the service turned on permanently for a few days and I’ve noticed little to no noticeable hit on battery life (probably due to the push notifications used instead of a persistent connection). Frugal data users will also be happy about that little setup.
When a message is sent, there’s no clear indication until you’re in the application itself that the message is a chat or text either via the home-screen or toast notification. Would be nice to know which is received but in the grand scheme of things it matters little I suppose.
In any case, I have little to complain about with regards to this implementation in either form or function and it’s a nice little addition. I’m interested to see how Twitter and eventually Skype fit into the equation but I can’t imagine them being any worse off for it.
Update
Upon updating to build 7712 I was met allowed to add my twitter account to the people hub. Much like MeeGo-Harmattan on the N9, your twitter timeline is readily available for your perusal. Like the events area on the N9, the What’s new section of the “people” hub shows updates from all your social networks and similarly can be easily filtered by twitter only, Facebook only, windows live only or all accounts.
Twitter is decently well integrated, providing notifications in the “Me” tile of mentions, Facebook updates and the like and allow for fast replies to tweets, comments or wall posts. With regards to twitter, it’s not quite a full suite of functionality; retweets and conversation threads are there but direct messages and “reply all” didn’t quite make the cut. In any case it’s a worthwhile and useful addition to the platform though highly unlikely to replace dedicated twitter applications at least in the short term
NB. LinkedIn is also available but I have little use for it at the current time
Turn by turn navigation
Whilst previously available in a myriad of additional applications, built-in turn by turn navigation finally arrives on Windows Phone 7 courtesy of Mango. Having tried it out a few times, it works. Whilst it doesn’t give as much granularity of control as Nokia Maps does with regards to taking only side roads, avoiding toll roads and the like it functions well enough for regular use.
It doesn’t quite update your location as much as I would like (which I’m sure will be hammered out for final builds) but the general interface and ideas are solid. You’re provided with the exact directions, i.e. which turn to take and distance to that turn, informative traffic information and upcoming directions in text and slightly graphical form at the bottom of the screen and a map at the top highlighting the route and current position.
The zoom level of the maps displayed is user controllable (via pinch to zoom of course) but generally varies to give a better idea of distances involved in your journey, closer zoom when turns are nearby, further out zoom when the turns are far away. A nice little touch is the presence of the aforementioned local scout icon just in case.
All in all a welcome and functional addition (powered by Navteq).
Miscellaneous additions
Office and cloud storage
Office integrates better with cloud based storage (though they all seem Microsoft based). I do hope for sugarsync/dropbox access in the near future though. Microsoft also provide 25GB of cloud storage via their Skydrive service and it is seamlessly integrated everywhere in the OS. Pictures, videos, documents can all be automatically uploaded to the cloud and vice versa. There’s even music access.
For even MORE cloud storage, there’s the Windows Home Server Phone connector that allows you to, as it says on the label, connect to your home server from your mobile device. Access there is only limited by your server’s capacity and your mobile bandwidth.
Music and media
The music player has seen a bit of an overhaul to the interface as well. It’s now much more easy to navigate and understand with more vertical scrolling as opposed to horizontal scrolling. There’s the “history” pivot in chronological order of course that scrolls vertically, the “new” pivot, the “apps” pivot where all media related applications (such as possibly Divx if it’s allowed) would accrete and the “Zune” pivot. Nothing earth-shattering but as they say, it’s the little things.
There’s now on-device podcast management, search and downloads and users can decide whether podcast download over 3G, Wi-Fi, or both.
The now playing screen also got a bit of a UI overhaul with all controls readily visible, cutting down on possible confusion for users. There’s repeat, shuffle and rating buttons and the list of upcoming songs is also at hand.
Tapping on the truncated list below the album art brings up the full list which thankfully fades away after being unused for ~15 seconds. Swiping in either direction with a finger on the album art functions as “forward” and “back” buttons and the album art allows you to see what you’re likely to be playing before you remove your fingers.
Tapping on the name of the Album drops you right into the respective artist’s section where you can view their albums, songs, bio(!) and a list of related artists.
You may have noticed a small “play” button with multiple sectors of a circle put to one side this is the smartDJ feature. This lets the music player create a playlist of songs based on a user chosen song or album. It works reasonably well within your own music library and with the most popular songs and artists but the real magic happens when you tie it to a Zune Pass account. When turned on in the settings, it allows Smart DJ to include songs in your little playlist from the entire Zune Music catalog and in reasonably high quality I might add. The small “broadcast” looking icon indicates that the song is being streamed. Streaming works equally well over 3G and Wi-Fi though slower 3G speeds and worse service do result in longer buffering times which are nigh non-existent on faster connections.
Music controls and album art are visible on the lockscreen for ease of use and aesthetic purposes but unfortunately, there’s no way to jump directly to the music player from the lockscreen. That said, a quick press of any volume key from any application allows access to all the playback controls AND the ability to jump directly into the music app by tapping on the song playing at that point in time.
The only downs in this whole setup are the missing equalizer and audio-altering options and somewhat convoluted playlist creation process. Playlists can be created by selecting a song or album and adding it to the “Now Playing” list. Tapping on the list allows you to save that list as a playlist.
As if you needed convincing, I’ll say this, coupled with a Zune Pass account, the music situation on Windows Phone 7 is easily the best implementation I’ve EVER used. If you need more information on what Zune Pass is, check out this post. If the service isn’t available in your region I’d still say that it’s one of the best implementations currently in terms of functionality, ease of use and simple aesthetic pleasure. I squeal at the thought of a Nokia device with an FM transmitter coupled with this thing.
Performance
The most succinct way of describing performance, even in this beta build, is quick, period. There is rarely a point where I’m waiting for the device to do something and those few points almost always relate to network access and downloading data and even then the device stays remarkably quick, unlike some other devices I’ve used. Transitions are fast and stay out of your way, never stuttering or keeping you from doing the things you want to do, even the loading/busy indicators are tastefully done throughout the OS.
Battery life for the device I’m using is decent enough that I never really worry about running out of juice during the course of a normal day though I can’t say that it’s “brilliant” but it is good enough for me. This however is not a fault of the OS itself but rather the display it’s using. A 4inch S-AMOLED display tends to suck juice like there’s no tomorrow. Doesn’t help that Samsung’s idea of a “low” power setting is what many devices would call 60% brightness and full power is simply blinding, literally.
Other
Changes to the mail app mean that users can “link” one or more mail inboxes together making them visible and accessible at the same time. Further to this is the addition of conversation threads where the mail-box automatically and intelligently links emails from a single user or under a single heading together.
I haven’t had any issues with this so far and it makes keeping track of email conversations that much easier. In essence if you have 4 different email addresses, multiple personal ones and a work one or multiple work ones and a personal one, you can group them together, name them “work” and “personal” and receive separate notifications and have separate inboxes for the two. Again, nothing earth-shattering but it’s a nice little touch.
Contact groups is another minor addition to the people hub, allowing users to create contact groups for quick and easy mass communication. This can be done through text, email or Facebook and I’m certain it’s a feature that some will find great use for. Microsoft has also done a nice little thing in creating a default “family” group which is populated by individuals with the same last name as you “supposedly” based on your phone contacts. Let’s hope you don’t have a lot of friends with the same last name eh?
Contact history is another nice and oft-forgotten feature in Mango, showing quite literally a history of communications and threads with any chosen contact in chronological order. Calls, texts and Facebook are all included here with breaks between threads based on length of time since last communication, form of communication used in the intervening time etc.
The camera can also automatically save user created settings and launches with them if the user so chooses (finally!)
Voice search and commands are somewhat improved now and allows users to literally operate the entire device by voice alone. Want to launch an app? You can do that. Want to search for something? You can definitely do that. Want to make a call and have speaker phone turned on when it connects? Yup, that works too. Want to text a friend? It’ll do that for you without you even opening the messaging app.
Coupled with the rather accurate and surprisingly fast (at least in English) speech to text engine you really don’t need to look at the device much at all to perform some of the most common tasks.
IE9
Supposedly it was meant to bring the browser up to par with the best on the market with HTML5 support and an improved rendering engine. To be fair in terms of performance I can’t quite argue with their claims in terms of rendering speed and accuracy compared to the previous version, the current version scores 95/100 on the Acid 3 test, 141 + 5 bonus points on the HTML5 test which measures how many of the HTML5 specifications the browser meets but says nothing of performance and completing the Sunspider 0.9.1 Javascript Benchmark test in 9631.7 ms almost a 500% improvement in Javascript performance.
Unfortunately this is still some ways behind the majority of Webkit-based browsers on the market, even those using the same SOC. All in all it’s still good enough for most people, mind there’s a rather obvious lack of Flash.
That said, in day to day usage, I want the old version back, just for the UI really. The old version provided 1-tap access to your bookmarks and tab-switcher whereas the current version does away with the icons and hides them in a menu. If you’re reading this Microsoft, bring the old UI back, yesterday; even if it means less visible browsing area, ease of access to the things we want is big deal. That said, each browser window does show up as a separate “app” (much like MeeGo) in the app-switching UI making it just a smidgen easier
What’s missing
I’m sure a few of you have very specific needs that your current or future devices absolutely have to meet in order for you to hand over your funds and fair do’s to you. There are even some that object to supporting the Windows Phone move on the simple grounds of disliking the company, others still on the grounds of “openness” and use those things as negatives when speaking in regards to the Nokia Windows Phone decision but none of those are concerns to me so I will not be considering them as “negatives” or things that are missing from the device of operating system.
Now that that’s cleared up there are a fair few annoyances and missing things that are OS specific, some of which I hinted at in my first review and further here.
Notifications:
Maybe Microsoft feel that live-tiles are/should be enough but it’s rather annoying not having to my notifications without having to go to the homescreen every time. Yes there are toast notifications but these are transient and permanent notifications often take up valuable screen real estate.
Further to this, one cannot directly access notifications from the lockscreen without swiping up then scrolling then finding the right email inbox/texting app/calendar etc. It’s certainly not impossible to implement, especially as both MeeGo-Harmattan and iOS5 do this in pretty damn decent fashion.
Similarly the system tray with battery indicators, network status and a few other things isn’t always visible in the applications that you’re using. Sure one could argue that seeing such things isn’t necessary all the time and they certainly take up useful real estate but making them more accessible is certainly preferred.
Roll better notifications and system tray into the improved volume control setup (which is both a transient UI element AND readily accessible) and users will thank you.
USB mass storage mode:
While the implementation of this feature would very much depend on OEM’s writing the right drivers etc for this, make it an option please, even if it means creating a minor partition in the NAND memory and only allocating that to non-.xap/.exe files. It’s quite a useful feature on Android and Symbian devices and will complement the cloud storage and data accessible everywhere approach you’re currently taking with Skydrive et al.
Video out/Mirroring:
We ALL know it can be done, we’ve seen you guys do it in demos while on stage, make it happen for us. And while we’re on the subject, getting screen caps on this OS is bloody hard. Can’t imagine that making a little utility for us that doesn’t necessitate installing the SDK and/or taking pictures of the screen with other devices or hacks
Multitasking UI and paradigm
I would very much like if I could see more than 5 of my most recent applications at any one time in the app-switching UI, even if the default is set to 5 for most users, the option to see more would be appreciated. Further to this dismissing which apps show up in this view requires having to jump into the app and tapping the back button idly ‘til the app reaches the default screen and THEN closing it.
Themes:
Self explanatory really
Conclusion: I have eaten the forbidden fruit (Mango) and strangely enough I like it, very much I might add. As an OS with a lineage barely a year from launch and ~18months from its initial announcement at MWC 2010 it’s come on by leaps and bounds to be honest. Is it good enough for me? In spite of it’s limitations I’d have to say unequivocally yes. Is it an OS that I’d recommend to my friends and relatives? In the Mango iteration, absolutely and without hesitation, something I haven’t been able to say about Symbian in quite a few years sadly.
As a standalone OS it works and works well but when connected to the full suite of services it really comes alive and is truly a wonderful experience. Unfortunately, due to the limitations of the current Marketplace for applications (not that many locales so far), lack of language support for some rather large regions and services like Zune Pass not being available everywhere your experience with Windows Phone can vary wildly.
It is for this very reason that Windows Phones by Nokia will only be launching in very specific regions and only those regions for the time being. The areas that support the full suite of services will get these devices first and all other markets getting the N9 and other Symbian devices.
That made it hard for me to give Mango an accurate numerical rating as the experiences may vary significantly and my rating will not hold true for many prospective buyers. If you’re in a region with full support for all the features offered with the OS and utilise them with the OS, Mango is just shy of a 9/10 whereas not utilising these features and being outside of the fully supported regions would leave it as more of a 7/10 product.
That said, I can honestly tip my hat to Microsoft for building something competitive, easy to use and user-centric in such a short period of time. Will Nokia succeed with this avenue? Who knows,but I’ll say this much, if it doesn’t it’s not because it wasn’t good enough.
Final Score: 8/10
I’ll also be taking questions in the comments, some of which will be added to the this post
Pictures from around the OS
Category: Nokia








Will Microsoft open stores like Apple that will cater to all wp7 or 8 devices? As a consumer that’s very important to me. I always have loved Nokia products but if something goes wrong you have to mail it off and stuck without a device unless you have a second device. That truly sucks, while at the apple store they either fix it or replace it and that’s so convient and hazzel free except time driving there and waiting your turn. Any ideal if Microsoft is going to follow suite like Apple with stores?
Apparently Microsoft are opening more Microsoft stores. It was reported some time frame ago that I don’t recall.
There is just something that doesn’t quite fit with MS stores. A store with the MS name on it, it just feels akward or something like that.
Perhaps a different brand for stores or something like the premium reseller concept from Apple would be better suited IMHO.
They’ve tentatively opened a few, I do wonder whether they’ll open more though.
There’s one about 15 minutes drive from my apt.
it got closed already
Which one do you refer?
u’ve got a stalker andre
Clearly
As far as I know, there are Microsoft stores but I don’t really see people fixing items there. I don’t go to it often but whenever I’m in Mall of America, I always stop by at least. The one at Mall of America is across the Apple Store.. lol.
Well there are already Microsoft stores around but I dont think there are many at all. I doubt they would be able to offer repairs to devices considering the array of manufacturers that they support.
Still very limited in o so many ways, Android still is more capable (symbian dead so not worth to mention, and even if iPhone has fake multitasking at least is not for only five apps, and the closing of apps far easier.
I made this clear in the review, more than 5 apps are multitasking. Only the most recent five show up in the UI. I complained about it there but it’s important to understand the difference.
If that’s the criteria that you’re using re:multitasking Android falls flat(er) than WP7.
Howso? on the SGS2 you just hold the home button, hit task manager, and hit close app or close all? And the list can go longer than 5 so I don’t see what you mean here.
Nice translation. It says: I have N9 take Nokia?
’tis better than my attempts at finnish.
Those usually go like this “…….. uhhhhh”
Goodness me, that is just boring.
Sorry
@Ninja or whoever might know:
Could you please provide a link to the info that WM is outselling WP (obviously, if possible preferably for markets where both are available)?
Thanks in advance!
Ok, did some digging and found that Gartner data suggests in Q1 2011 about 2 million WM and 1.6 WP.
I suspect a big part of this is indeed due to availability. For example, a few years ago WM used to be the most popular smartphone platform in Japan, and there may still be fair residual sales there. Whereas WP is not yet available there, AFAIK, and is only now about to launch with Mango.
Note: I am not trying to claim WP sales are great, just trying to understand the situation more precisely and accurately.
I love it when people answer their own questions
Nothing wrong with doing a bit of research and trying to give some nuance to the arguments, is there?
You found the Gartner’s Q1 report already. Well I’m gonna post this anyway in case someone want’s to look the numbers too.
Here are links to Gartner’s Q1/2011 worldwide OS sales report and the USA smartphone OS share (March 11-May 11) from Nielsen:
GARTNER (Q1/2011):
http://www.wpsauce.com/2011/05/according-to-gartner-microsoft-sold.html
NIELSEN (March11-May11):
http://blog.nielsen.com/nielsenwire/?p=28237
Newer ones from Nielsen or Canalys don’t separate WinMo and WP7. Here are those newer Q2 reports regardless:
NIELSEN (Q2/2011):
http://blog.nielsen.com/nielsenwire/?p=28516
CANALYS (Q2/2011):
http://www.neowin.net/news/wp7-hit-by-abysmal-sales-android-soars-to-50-of-market-in-q2-2011
Those definitely did sealed the deal. Some of the problems with it are just too minor for me to give a damn, and the complete overhaul will definitely give me a better UI experience. Can’t wait for Sea Ray.
If I could just hold on to my N8 until Nokia puts out their top camera phone with WP.
I love knowing my N8 can do all kinds of cool stuff, but have I ever used those features… No.
Bingo.
Neither Apple nor Android and Symbian really multitask in my opinion and this is coming from a maemo 5 user. They look as though they suspend the app or pause it until you come back to it. N900 multitask like no other device I’ve ever seen. I can say from trying the windows devices the marketplace is the most beautiful ui for apps I’ve ever seen and that’s even including Itunes. I think the hardware companies for windows 7 did a horrible job promoting windows os and not microsoft.
@Rudeboi…They really did. Basically, HTC, Samsung, and LG threw WP a bone and used the same, tired Android device shells for their WP offerings. WP was an afterthought for them, and by the looks of some of the HTC leaked WP devices, it’s going to be more of the same.
^^^This^^^is why (amongst other reasons) so many WP fans are excited about the Microsoft/Nokia partnership – We know Nokia can design some unique, stylish phones that won’t look like a ‘sea of sameness’ Android device. It’s a ‘little’ disappointing that Nokia is using the same shell for the SeaRay as they are for the N9, but I realize that they had to get something to market this year. However, I’m hopeful that all future 12+ devices that Nokia releases in 2012 will have a unique look unto themselves, not shared by any other Nokia device.
only “some” java apps get suspended on symbian.
“Neither Apple nor Android and Symbian really multitask in my opinion and this is coming from a maemo 5 user. They look as though they suspend the app or pause it until you come back to it. N900 multitask like no other device I’ve ever seen”
Well, you are wrong in the case of Symbian. From http://en.wikipedia.org/wiki/Symbian
“Symbian features pre-emptive multitasking and memory protection, like other operating systems (especially those created for use on desktop computers)”
What the kernel supports is often has little to do with the implementation of “multitasking” for third parties.
The Linux kernel, mach/bsd kernel at the root of iOS and windows CE which underlies WP7 all support multitasking in one form or another.
I’m not talking about what the kernel supports.
Symbian supports preemptive multitasking and doesn’t need to have software written in a specific manner as “more modern” iOS, WP7 and Android needs, it multitasks it.
Symbian preemptively multitasks C++ and Java (J2ME) apps or even Python scripts.
My N82 did that and my N8 too. Well, I didn’t try Python scripts with my N8.
Isn’t Symbian multitasking primarily event driven?
What does that mean? How does it affects the fact that Symbian can preemptively multitask Symbian C++, Qt, Java etc applications?
Means unless the dev writes the app to work in the background when specific events occur, the application won’t run properly or fully.
Just so you know, NONE of the OS’s mentioned above differs that significantly in the way they multitask.
Symbian & Windows CE are real time multitasking OS’s with Symbian using pre-emption and CE using a different form of scheduling.
iOS is pre-emptive in it’s multitaskiing as well.
That said, DEVELOPERS are not given full access to the scheduler et al in iOS or WP7 in part because they’d likely f*** everything up
.
So your comment about more modern OS’s requiring software written in a special form is moot on two fronts
nokia will regret when other manufacturers produce meego phone
meego is good out of the box
You understand that Nokia’s UI is proprietary? It’s the UI that matters, have you ever seen MeeGo’s reference UI?
Exactamundo! I wonder when we will see the first, full blown Meego phone device? The progress on Meego proper is pathetically slow….
On the Meego tablet front we might see some movement. Maybe.
maybe china can use meego so they can screw uncle sam err I mean android.
Translated:
Can I have an N9 please Nokia
-> I have ap N9 take it Nokia
very long post.
do we’ll see long post like this from mnb if N9 come or this just for wp?
If I end up doing the N9 review then yes
It’s enough to see Acrobat Reader in the screenshots. What is the purpose of seeing a pdf reader icon. One never starts reading PDF from A Reader. They just don’t get it… Goodbye Nokia!
One *rarely* starts a PDF from the application but youd be wrong if you thought the designers were idiotic enough to mandate you use the app to open all PDF files regardless of location. Like any intelligent OS if you have an application on your phone that handles a certain file extension, that application will launch automatically and run the file when the user clicks it.
If you get a word document or PDF via email or dropbox etc you tap on the file and the right application launches.
Andre: “If you get a word document or PDF via email or dropbox etc you tap on the file and the right application launches.”
Exactly!
The question is why do they always leave the icon even visible since it takes up space.
Another reason for hiding it is usability. Which is easier and faster , selecting an action from 9 icons or from lets say four. Often in MS and Nokia products they tend to overlook the fact that there are many icons people rarely press at all. They should get rid of anything unnecessary.
This thing is so elementary mistake they make. They obviously haven’t read any usability guidelines.
From a usability standpoint, you hamper rather than help the user in the specific scenario you mentioned. first of all is the fact that the adobe app aggregates all pdfs on the device in one readily accessible place meaning that users don’t have to be digging around wondering which folder, subfolder, email and email account they chucked the PDF in.
Its less a mistake and more of a conscious design decision and a good one I might add
Agree. I at least on my desktop/laptop often go to Adobe to open files I had opened recently, rather than go digging for them in my file manager.
I understand, but as you said: “One *rarely* starts a PDF from the application”
The rarest things should be hidden. But it’s just a matter of opinion… Apple doesn’t have Acrobat visible. In my Nokia, I have never pressed that.
Documents should be in “Documents”. Who cares if it’s a PDF or a .doc. This is not desktop computing.
After reading all post and comments from many reader, i still in the opinion that many people still not convinced about WP7 at the moment. Blog owner also heavily presented during discussion and up holding his review.
Currently I’m holding N8(still in service center !!!), N86 8MP (main business line with full broadband access) and E71 (backup phone line), my wife is using iphone 4 now and she is so happy with it and never seen this when she is using Nokia for past 10 years !
I definitely will buy N9 when it is available, and keep observation to Nokia WP7 only for year to come. I also eying at SGS2, while pending release of iph5, IF N9 failed.
@Andre.
My comment don’t seem to appear and the borad complains that I posted already.
“Means unless the dev writes the app to work in the background when specific events occur, the application won’t run properly or fully.”
How so? How do the Python scripts and Java apps which are platform agnostic manage to run in the background? What trickery do they use?
“Just so you know, NONE of the OS’s mentioned above differs that significantly in the way they multitask.”
Symbian apps are not just frozen in memory, regardless of how they are coded, if you start a task and decide to swithc to another. There is one exception, the videoplayer, and I’m willing to bet that it was a conscious decision from Nokia.
“Symbian & Windows CE are real time multitasking OS’s with Symbian using pre-emption and CE using a different form of scheduling.”
“iOS is pre-emptive in it’s multitaskiing as well.”
Apps need to be written in a specific matter, and then again, there are only a few activities that are allowed to run, not just sit in memory, in the background. If your app needs to do something else than what Apple decided was allowed, you’re SOL.
“That said, DEVELOPERS are not given full access to the scheduler et al in iOS or WP7 in part because they’d likely f*** everything up
.”
Well Symbian apparently has no such restrictions. Why would they want to have access to the scheduler? The scheduler is in charge of deciding when allocating run time to applications. Well, in “less modern” OSes like Symbian or desktop OSes.
“So your comment about more modern OS’s requiring software written in a special form is moot on two fronts”
Tell that to the person who wrote this : “Multitasking:
Another one of the big additions in Mango is multi-tasking. Unfortunately it doesn’t quite work for 3rd Party apps, at least until developers recompile their applications for Windows Phone 7.1 (aka Mango) instead of Windows Phone 7.0. As such, the BEST multitasking experience is limited to built-in applications. That said, all indications point towards minimal work at best on the part of developers which will ensure a good experience for end-users.”
My first comment refers specifically to native Symbian C++ applications, I have no clue how the Java engine or the python interpreter actually run on Symbian.
—>”Symbian apps are not just frozen in memory, regardless of how they are coded, if you start a task and decide to swithc to another. There is one exception, the videoplayer, and I’m willing to bet that it was a conscious decision from Nokia.”
You sure about that? Because I have a few stopwatch applications that didn’t quite time properly unless they were in the foreground
—->”Apps need to be written in a specific matter, and then again, there are only a few activities that are allowed to run, not just sit in memory, in the background. If your app needs to do something else than what Apple decided was allowed, you’re SOL.”
—————————
Well that’s Apple’s decision in order to preserve their UX. But all OS’s have certain restrictions on what API’s devs are allowed to use and at what time. It’d be stupid to give a game access the the 3d and 2d rendering engine while the UI is being rendered and the game is not the active window etc. The thing is, the more freedom you give, the less reliable and more prone to failure your OS is. It’s a balancing act that all have to play, some just have less restrictions than others and it’s fair to say that the UX’s across the board are in a fairly distinct inverse relationship to restriction level.
—->“So your comment about more modern OS’s requiring software written in a special form is moot on two fronts”
Tell that to the person who wrote this : “Multitasking:
Another one of the big additions in Mango is multi-tasking. Unfortunately it doesn’t quite work for 3rd Party apps, at least until developers recompile their applications for Windows Phone 7.1 (aka Mango) instead of Windows Phone 7.0. As such, the BEST multitasking experience is limited to built-in applications. That said, all indications point towards minimal work at best on the part of developers which will ensure a good experience for end-users.”
————-
Recompile != rewrite. It’s like expecting your application for Symbian 8.0 to work on Symbian 9.4. Good f***ing luck without a recompile and with API changes in the two versions of the UI you’d be daft to expect the two to run exactly the same. Further to this, if you don’t have certain API’s in a prior version of the OS, but new API’s in a newer one that make your multitasking experience better, for very very obvious reasons, you have to modify your code to incorporate them. This applies to Symbian too and that’s the point I was trying to make.
More modern OS’s are no different than “less modern” OS’s in terms of requiring developers write their programs to take advantage of the API’s available and that’s what I meant by “special form.”
Sorry if I wasn’t clear.
“My first comment refers specifically to native Symbian C++ applications, I have no clue how the Java engine or the python interpreter actually run on Symbian.”
Apparently well enough since Java apps and Python Scripts are preemptively multitasked.
“You sure about that? Because I have a few stopwatch applications that didn’t quite time properly unless they were in the foreground”
So what? Do your stopwatch applications work at all on iOS/WP7/Android in the background if the dev didn’t have to make use of special multitasking API? Timer performance issues are nothing new.
“Recompile != rewrite. It’s like expecting your application for Symbian 8.0 to work on Symbian 9.4. Good f***ing luck without a recompile and with API changes in the two versions of the UI you’d be daft to expect the two to run exactly the same.”
I can’t run WP7 apps without a recompile on WP7.1?
“Further to this, if you don’t have certain API’s in a prior version of the OS, but new API’s in a newer one that make your multitasking experience better, for very very obvious reasons, you have to modify your code to incorporate them. This applies to Symbian too and that’s the point I was trying to make.”
What special APIs have to be called in Symbian to “make my multitasking experience better”?
“More modern OS’s are no different than “less modern” OS’s in terms of requiring developers write their programs to take advantage of the API’s available and that’s what I meant by “special form.””
I spend my working hours in Visual Studio, and I don’t do anything special to the apps I write, and they multitask just fine.
“Sorry if I wasn’t clear.”
Don’t be. You’re just trying to prop up WP7 on an area where it’s inferior to Symbian, that’s all.
I’m not trying to prop anything up, you’re trying to tear something down when there really is no reason to do so.
When you compile applications for Symbian if you used the right API’s it’ll run the way it should. Same situation goes for EVERY other OS on the market, bar none.
If your python scripts run in the background as you suggest, can you right a python script that iterates through a set of numbers up to a defined point and completes itself in a certain amount of time in the foreground and similarly put the task in the background and get the same result?
I can send you a simple python script right now if you’d like.
You say they multitask but is it due to the OS not placing any restrictions at all? And where do you deploy your visual studio applications.
“I’m not trying to prop anything up, you’re trying to tear something down when there really is no reason to do so.”
The point of contention is that iOS/WP7/Android and Symbian multitasking are similar. They are not.
Symbian is a preemptive multitasking OS, like desktop OSes.
iOS/WP7/Android run task in the background if you write them in a specific way.
I don’t see why this is open to debate.
“If your python scripts run in the background as you suggest, can you right a python script that iterates through a set of numbers up to a defined point and completes itself in a certain amount of time in the foreground and similarly put the task in the background and get the same result?”
Even in a desktop OS there is a variation of performance, what is your point?
“You say they multitask but is it due to the OS not placing any restrictions at all?”
It’s due to the OS that uses its scheduler to allocate runtime to apps with no special work on my part. You know, preemptive multitasking.
“And where do you deploy your visual studio applications.”
On the desktops of my coworkers and some Terminal Servers. What difference does it make?
I know what pre-emptive multitasking is, I know what real-time OS’s are, I know how schedulers work.
The point I was trying to make though is that from a kernel perspective the OS’s aren’t that different and ditto for first party applications.
I concede that there are significant differences for 3rd party users but they’re really not THAT different IMHO. WIth Symbian there’s the option of 3rd parties not writing the application to best take advantage of the background processing API’s whereas with the others that’s not the case. If I’m getting this right that is.
PS. YOu shouldn’t deploy any applications to a new version of an OS without looking at the documented API changes and general changes to the OS unless the OS creator specifically says that your applications are backwards compatible/running in an emulated environment a la windows.
“PS. YOu shouldn’t deploy any applications to a new version of an OS without looking at the documented API changes and general changes to the OS unless the OS creator specifically says that your applications are backwards compatible/running in an emulated environment a la windows.”
Thanks for the unsolicited advice.
…….seriously?
You could have been a little more……. pleasant with your response. I’m not having a go at you or saying your opinion is wrong or anything, this is a learning experience for me as well.
Because if what your saying is true you’re clearing up certain misconceptions and misinformation I have on Symbian. Take it easy will ya.
“You could have been a little more……. pleasant with your response. I’m not having a go at you or saying your opinion is wrong or anything, this is a learning experience for me as well.”
Ok. It’s a misunderstanding, as it often happens with written communication.
No hard feelings on my part.
When he was talking about 3rd party apps it doesn’t mean developers have to rewrite their apps, just recompile them with the new tools.
Every application compiled with the latest tools will support fast resume. For background services you will have to write code but this should be the same practice on every OS no matter the platform. Your application should adapt to the state it is in.
“Every application compiled with the latest tools will support fast resume” is different from preemptive multitasking, don’t you think?
Instant resume gives the illusion of multitasking. The issue he was complaining about with 3rd party apps was in the first version of WP7 apps had to load each time they were opened but with Mango they resume instantly if they are compiled with the latest tools which gives the applications a feel of multitasking. It is pretty brilliant, feels so fast and yet battery life actually improved with the update!
Every app also has preemptive multitasking abiltities if you compile/build with the latest tools, but you of course have to implement them. You don’t have to rewrite your code but since these api’s were not there before you have to add code to make it work similar to what you have to do with any OS when a new api is introduced.
They actually have a pretty in depth multitasking scheme. You don’t have a full application running to make it happen but by using a combination of deep linking, messaging, background tasks and instant resume you have the illusion of true multitasking wihout the overhead. Windows Phone application model is really pretty amazing. It has a much sought after secure sandboxed approach which keeps things running blazingly fast and secure but hides it so well you would never realize it at least from a users perspective.
“Every application compiled with the latest tools will support fast resume”
“fast resume” is different from preemptive multitasking, don’t you think?
Very nice review! Been using Mango the past month or so as well and really love it. Such a streamlined OS. Prefer it over my android phone and iphone. Easy to see why Nokia picked Windows Phone 7 after this past month.
The home screen/live tiles really solve so many issues it is hard to use any other OS afterwards and I do dissagree about your “”missing notifications”" somewhat because of this. I find the live tiles in combinations with the “me” “contact” and “group” tiles to offer a much more advanced yet enjoyable way of doing/seeing notifications. When I switch over to Android and IOS I really miss this approach.
Acting on popup notifications is also done very well although pretty much every mobile OS can say this now, but Windows Phone 7 still manages to make it feel more enjoyable, streamlined and unobtrusive.
And it just feels so dang fast! Crazy to think we are using this on old hardware, can’t even imagine how fast this will feel on the new generation of devices and especially from Nokia!!
Great post babe! I’m not finished reading it, but I’m working on it!!!
“Unfortunately it doesn’t quite work for 3rd Party apps, at least until developers recompile their applications for Windows Phone 7.1 (aka Mango) instead of Windows Phone 7.0.”
AFAIK, No-do is Windows Phone 7.1 while Mango is Windows Phone 7.5, isn’t it?
This is so funny to see Openness “apostles” so “closed” and narrow minded…
WHAT ABOUT ADOBE FLASH ? A LOT OF OTHER THINGS ARE NEEDED BUT ADOBE FLASH IS A MUST HAVE.
It’s really a cool and helpful piece of info. I am glad that you just shared this helpful info with us. Please keep us informed like this. Thank you for sharing.