How does WP stack up against iOS and Android as an OS (so apart from the app gap)

[fatclue_98]

That hasn't been anywhere near MY experience unless we're talking about the BlackBerry Playbook :eck: Do have a few Android/iOS devices with 1GB (or less) of RAM with applying updates/updating apps being a far different outcome for me over WP/WM, less time and the least amount of user input.

Updates 2 apps! My Android/iOS devices can have 5 apps updated in the time it takes just to initiate the process on WP/WM, seriously it's pathetic. If it has come down to needing a higher-end CPU and more ram to accomplish this feat alone then something ain't right here.

I'm fully aware something less powerful will struggle more than the higher end, but if I'm seeing similar traits playing out on a W10 PC w/i7/8GB RAM/SSD then something tells me MS got things a little askew, on both mobile and PC, as to the proper way to implement updates... Guess though in this instance, since we got the upgrade to W10 for free, we get what we DIDN'T pay for, here too. :winktongue:

In MY experience, I've never spent more than 45-60 minutes to set up a new Windows phone from a backup. That includes 640s and other low end phones. I used to dread hard resets but this Idol rips through the process in well under an hour with updates and all. Obviously your mileage has indeed varied.

Sent from Alcatel Idol 4S with Windows via mTalk

 

[slivy58]

In MY experience, I've never spent more than 45-60 minutes to set up a new Windows phone from a backup. That includes 640s and other low end phones. I used to dread hard resets but this Idol rips through the process in well under an hour with updates and all. Obviously your mileage has indeed varied.

Sent from Alcatel Idol 4S with Windows via mTalk

That's another thing with me, not quite sure why but never had all that much luck w/backups on WP. At this point and time we just want to give the 650 an honest go and see how it fairs under daily usage, think if we can achieve that goal without too many hiccups we'll be a relatively happy camper. :grin:

 

[fatclue_98]

That's another thing with me, not quite sure why but never had all that much luck w/backups on WP. At this point and time we just want to give the 650 an honest go and see how it fairs under daily usage, think if we can achieve that goal without too many hiccups we'll be a relatively happy camper. :grin:

That's the spirit!

Sent from Alcatel Idol 4S with Windows via mTalk

 

[libra89]

Maybe I'm just weird but to me, iOS felt like it was the quickest with setup when it comes to a new phone. Android has varied with the phone but it could take just as long as a Windows Phone or be longer.

 

[fatclue_98]

Maybe I'm just weird but to me, iOS felt like it was the quickest with setup when it comes to a new phone. Android has varied with the phone but it could take just as long as a Windows Phone or be longer.

For the very reasons I mentioned to Elky64 - horsepower. Even the little SE has the A9 chip and iOS has never needed 40GB of RAM to function properly. Any Android without flagship specs will be an exercise in patience. Give Mother Teresa an $80 Blu and she'll make Andrew Dice Clay blush.

 

[libra89]

For the very reasons I mentioned to Elky64 - horsepower. Even the little SE has the A9 chip and iOS has never needed 40GB of RAM to function properly. Any Android without flagship specs will be an exercise in patience. Give Mother Teresa an $80 Blu and she'll make Andrew Dice Clay blush.

That's a great point. I do believe you on that.

 

[slivy58]

That's the spirit!

Sent from Alcatel Idol 4S with Windows via mTalk

We've been trying, trust me we have :smile:

 

[tgp]

In the midst of all that you're constantly notified and required to do so... "your language was just updated, a restart is required", "Glance was just updated, a restart is required", blah blah blah.

Setting up my 650 wasn't as painful as you described in your post, but I did come across an interesting scenario that applies here. I turned off Touch vibration, and it said a reboot was required. I was quite surprised, to put it mildly!

I agree with you that setting up a WM device is more hassle than doing the equivalent on iOS or Android. Just getting all updates installed was an exercise in patience!

 

[fatclue_98]

Setting up my 650 wasn't as painful as you described in your post, but I did come across an interesting scenario that applies here. I turned off Touch vibration, and it said a reboot was required. I was quite surprised, to put it mildly!

I agree with you that setting up a WM device is more hassle than doing the equivalent on iOS or Android. Just getting all updates installed was an exercise in patience!

In my humblest of opinions, I believe WM is going to become a resource hog like Android requiring lots of RAM to function at a basic level. I'm not a programmer but I believe this cohesiveness with desktop is slowly contributing to the problem. Just look at Facebook, you need 2GB to get it to run. I'm no expert but I don't think ANY app should require that much horsepower. Maybe when x86 on ARM rolls around that may be the case but certainly not now with present hardware. Oh well, it's not like MS hasn't pulled this stunt before.

Sent from Alcatel Idol 4S with Windows via mTalk

 

[mattiasnyc]

But again, we should separate apps from the OS, the two aren't the same. Google+ and Facebook made my G2X unworkable on Android. I can't blame Google for Facebook's performance, only for that of Google+.

Of course we could argue that the OS vendor shouldn't allow heavy apps on OS that can't handle it, or on phones that can't handle those OS' or apps, but then we're stuck with a likely lack of progress as apps bloat, or a slower progress, along with complaints not only of that but also aging hardware, neither we can then do anything about.

In other words, if Facebook is a resource hog I'm not sure that's either Google's or MS' fault. Or Apple's. And then we have to decide if we want to artificially limit what an OS can become based on the resources it would consume. Is that what we want? No? Then we need to just accept that either future OS won't run on smartphone X because it's too old and slow and we get a new phone, or we run the new OS on an old phone and it gets sluggish.

I just don't see much of a way around this.

 

[fatclue_98]

But again, we should separate apps from the OS, the two aren't the same. Google+ and Facebook made my G2X unworkable on Android. I can't blame Google for Facebook's performance, only for that of Google+.

Of course we could argue that the OS vendor shouldn't allow heavy apps on OS that can't handle it, or on phones that can't handle those OS' or apps, but then we're stuck with a likely lack of progress as apps bloat, or a slower progress, along with complaints not only of that but also aging hardware, neither we can then do anything about.

In other words, if Facebook is a resource hog I'm not sure that's either Google's or MS' fault. Or Apple's. And then we have to decide if we want to artificially limit what an OS can become based on the resources it would consume. Is that what we want? No? Then we need to just accept that either future OS won't run on smartphone X because it's too old and slow and we get a new phone, or we run the new OS on an old phone and it gets sluggish.

I just don't see much of a way around this.

From what I read elsewhere on this site, the Facebook issue is a Microsoft issue having to do with UWP. Someone please correct me if I'm wrong.

Sent from Alcatel Idol 4S with Windows via mTalk

 

[tgp]

In my humblest of opinions, I believe WM is going to become a resource hog like Android requiring lots of RAM to function at a basic level.

Yes, I believe that Android and WM have already switched places. I think WM took that "crown" awhile ago, with W10M.

As I see it, this hype about W10 on ARM has downsides in resource requirements and security. I don't think it is a good solution to Microsoft's mobile dilemma. But then again, I think it's the fan base hyping it up as Microsoft's answer to mobile more than anything.

 

[mattiasnyc]

From what I read elsewhere on this site, the Facebook issue is a Microsoft issue having to do with UWP. Someone please correct me if I'm wrong.

I searched and found nothing like that.

 

[mattiasnyc]

As I see it, this hype about W10 on ARM has downsides in resource requirements and security. I don't think it is a good solution to Microsoft's mobile dilemma. But then again, I think it's the fan base hyping it up as Microsoft's answer to mobile more than anything.

Obviously full Windows 10 has higher requirements than W10 Mobile. Whether or not that's a downside is debatable. We all want more for less, but sometimes physics just get in the way of that.

As for it being hype as an answer to some sort of "dilemma" it really isn't I think. IF you can run regular Windows 10 on ARM devices, AND they're powerful enough then you absolutely solve a lot of issues for mobile that non-users repeatedly complain about. The "app-gap" gets turned upside down when you have access to all Windows 10 apps, UWP or not. Obviously, a heavy app that need great hardware will end up in an expensive hardware purchase, but that's beside that point.

It really is a completely new situation. If you look at the one big competitor in the personal computing space, Apple, you'll see a clear distinction between mobile devices with OSX and those with iOS. The device types are very different. Everything I've seen MS say about mobile's future, including the Surface department's general views on innovation (or development), tells me that MS wants to get users to use MS Windows 10 along with the surrounding ecosystem, regardless of device form factor and functionality. So, it seems they want to streamline it all so that you experience Windows 10 on any device you use, regardless of how you input data and get it back. So what we've been stuck with so far is that as device sizes hit a certain 'smallness' we move from x86 to ARM, because of power consumption and radio. And then we've just gotten used to that being on tablets and smartphones. Now, rather than having to make a decision about whether to shove an iOS or OSX CPU into a tablet-size device like Apple 'has to', a maker of an ARM device can choose to put Windows 10 on it. Period. They can market it any way they want, but it's a Windows 10 device.

So Windows 10 Mobile, in my opinion, still has a place here. For less horsepower consuming apps and longer batter life etc a smaller lighter OS makes sense, to me at least. And then it scales seamlessly across the eco system as you switch devices.....

 

[mattiasnyc]

"batter life".... lol....

 

[fatclue_98]

Obviously, a heavy app that need great hardware will end up in an expensive hardware purchase, but that's beside that point.

Actually, I think that IS the point. The Elite x3 is not moving the needle one iota (according to AdDuplex) and it's not even going to be able to run W10 on ARM when it eventually comes out. Many consider the device too expensive as is so imagine what will happen to our lowly numbers when really expensive hardware will be required.

 

[mattiasnyc]

Actually, I think that IS the point. The Elite x3 is not moving the needle one iota (according to AdDuplex) and it's not even going to be able to run W10 on ARM when it eventually comes out. Many consider the device too expensive as is so imagine what will happen to our lowly numbers when really expensive hardware will be required.

The point of Windows 10 on ARM is that you can run Windows 10 on ARM. People not buying a Windows 10 Mobile device because it's too expensive is a completely different issue. It says nothing about what people want to pay for a Windows 10 (non-"Mobile") device running ARM.

So, as an example; suppose you have a user that is happy using bluetooth headsets for listening to music and talking to people. Now, this person doesn't mind a very large screen. In the Apple ecosystem, large screen that isn't a laptop means tablet, an iPad. Still need a phone though, which in turn means iPhone. Pretty expensive. Suppose the person also needs OSX because of some OSX-specific software. Three devices now. But for those users that are wiling to pay for two, or even three devices, but really want a large screen that's close to tablet size (perhaps foldable), but with cellphone capability, and preferably also the ability to run a desktop app, for those users an all-in-one smaller form factor mobile device will make complete sense.

So rather than get a Lumia 950 for like $400, a tablet for $500, and a laptop for $1000, you'd get that smaller device which does it all (with compromises). At that point it could cost you $1,200, and you'd still be saving $700 relatively speaking. Know what I mean? So that's why you can't compare the two.

It'd be like saying that people are upset over the iPhone being expensive so they wouldn't buy one that ran OSX. Apples and oranges.

 

[Joe920]

I just discovered that force touch on the iPhone keyboard turns it into "move cursor". Awesome! Super zippy. It's way more convenient than the pretty clever WP joystick/trackpoint in the keyboard.

 

[Joe920]

Now that I own a 6S+ I guess I'll just keep going with little OS differences that I notice.

Here's one: on iOS when you clear a text message notification from the lock screen, it actually marks the message as read, and removes the corresponding 'badge' counter on the icon. On WP the unread counter doesn't budge, and the message still shows unread iirc.

 

[mattiasnyc]

Now that I own a 6S+ I guess I'll just keep going with little OS differences that I notice.

Here's one: on iOS when you clear a text message notification from the lock screen, it actually marks the message as read, and removes the corresponding 'badge' counter on the icon. On WP the unread counter doesn't budge, and the message still shows unread iirc.

From what I can tell from memory, that's actually not necessarily a bad thing (for me at least).

While it could be practically annoying to have things marked unread if you feel like you've read them, to me it actually makes sense in some cases because the lock-screen notification message isn't the entire message. Same with the drop-down menu. Clearing the listed new messages there, including emails, won't mark them read, and it makes sense since in a lot of cases my emails are far longer than the preview that is shown.

So from that standpoint it makes sense. To me. Unless I misunderstood something or am remembering incorrectly.