Should Microsoft allow OEMs more customization options in WP?

[TechAbstract]

Android allows OEMs to customize many parts of the UI. It's one of the reasons why the OEMs favor Android. Should Microsoft open this part of WP to bring more OEMs to WP?

 

[Harrie-S]

No .

 

[tuxedo323]

I don't always smartphone, buy when I do, I WP.

No.

Stay secure my friends

 

[Tom Raccoon]

No. The current policy of allow OEM to add features, but without changing the existing ones, is quite enough.

 

[Rodrigo Mendes]

I think the Microsoft customization is something between IOS and Android. I my opinion is the best way to lead with it and Microsoft would not change anything about it.

 

[a5cent]

This is precisely one of things Google is now desperately trying to reign in and get back under their control. It would be pure irony if MS started to bork another one of the things they got right, by copying Google, after Google themselves realized it was the wrong choice.

OEMs can already change a lot on their own, and MS is always happy to help develop any APIs OEMs feel are missing. The camera API for the 1020 or the ability to support HTC's dot view case are examples. That's a big part of what the GDR releases are for.

In the interest of keeping the user experience consistent and fast, skinning or replacing the UI should remain off limits.

OEMs can still provide their own custom backgrounds. The live tiles for their own apps can also look however they want them to, so OEMs do have options.

 

[TonyDedrick]

I say why not? As long as it doesn't get too wild or sacrifices usability, I say let them do some fun things with the OS.

 

[rollindice]

Nope,love it this way,let oem bring better design ,hardware features and software only those oem brands would have,for instance,the range of Lumia camera apps,story teller,sms+ filter,here maps,etc.

 

[prasath1234]

I am in for that idea.OEM needs customization to stand out from other OEMS.

 

[Harrie-S]

I am in for that idea.OEM needs customization to stand out from other OEMS.

If OEM want to stand out they should/can use the design of the device they do not need the OS for this.

 

[Dk92]

I say why not? As long as it doesn't get too wild or sacrifices usability, I say let them do some fun things with the OS.

I agree, and if you want your phone to remain how it currently looks, just get a Microsoft Mobile device.

 

[a5cent]

I am in for that idea.OEM needs customization to stand out from other OEMS.

Hasn't Nokia, by gaining 90% WP market share, already proven that an oem can stand out without having to mess with the UI? It just requires some effort, beyond recoloring a UI and passing it off as innovation.

 

[SammyD97]

No.

 

[aximtreo]

I don't always smartphone, buy when I do, I WP.

No.

Stay secure my friends

Good play on words. Nice way to make a point.

 

[envio]

No. Definitely not. Never.

Ok, so it's easy to say "no" but one the main reasons that sets Windows Phone apart from the plethora of Android offerings is that no matter which OEM you choose, the base OS user experience (UX) should remain rock solid no matter whether you choose a budget value or mega flagship product. That's not an easy feat to pull off but it does require the OEM to think differently in terms of differentiation and it's entirely possible.

Arguably, Nokia did (at the time) have a slight advantage over other OEMs when they joined the WP family as they were given deeper access to the underlying OS. However, notice that they didn't break any of the fluidity, simplicity or uniformity, they instead mostly leveraged it to enhance their imaging offering for example. Everything else was largely optional through apps, except for a system level apps that are otherwise non-removable. Plus they continued to innovate and provide app updates and new apps and tailored accessories etc.

And that's what the OEMs have to do - couple a great hardware product and accessories along with unique OEMs apps and tools that enhance the user experience without affecting the overall look 'n' feel or hurt underlying performance. That's the right balance between Apple's totally closed shop and Google's utterly open and often abused alternative.

 

[JamesDax]

No!

 

[nessinhaw]

hell no! Android is more than a better example of what happens when you allow OEMs to do as they wish! it ended up getting out of control and we have stuff like Touchwiz or Android phones loaded with useless bloatware you can only completely remove thru rooting!

the way WP works, the UI is consistent and clean and aside from system apps, we can easily uninstall everything else!

and this is too much of a good thing for MS to spoil it trying to copy Google and the "mess" Android became with lots of different OEM customizations and bloatwares!

 

[Toan Le]

No. MS is trying to unify their OSes - Windows, Windows Phone, Xbox - all with the same design language, same experience. Now, if they let OEMs mess up with MS's own design, will Windows Phone be what it should be, with all these simplicity and Metro design? Will the three OSes bring unified experience, if Windows Phone are customized, just like Android? And also, OEMs may ditch Live Tiles for icons, who knows? Windows Phone with icons? Bah.

 

[a5cent]

Arguably, Nokia did (at the time) have a slight advantage over other OEMs when they joined the WP family as they were given deeper access to the underlying OS. However, notice that they didn't break any of the fluidity, simplicity or uniformity, they instead mostly leveraged it to enhance their imaging offering for example.

While it's true that Nokia gained the right to modify the source code of the OS, they never exercised that right. As such, any slight advantage Nokia may have arguably had was purely theoretical in nature, because in practice they never exercised that right.

Everything related to Nokia's imaging they did through firmware, even for the L1020. What Nokia couldn't do in firmware alone MS was asked to provide for them, or at least provide a few more extension points so the firmware could hook into the OSes processing path where and when required.

 

[fatclue_98]

Definitely not. Part of the allure of WP is that you can go from one device to another without a learning curve. Carriers and OEMs are already allowed to bundle their own specific apps and that's good enough to differentiate one from another. The fact that bloatware can be uninstalled without "rooting" or any other warranty-voiding processes is good enough for me.

Now if developers want to add window dressing to their WP apps to make them stand out from their Android or iOS counterparts, I say have at it.