If you look at what Microsoft is doing with Windows 8, they’re actually (for once) doing something great when it comes to providing built-in app updates. Those updates are all going through the Windows Store, which means there is no need to wait for Microsoft to push a major OS update in order to update those built-in app. So apps like Mail, Calendar, People, Music, Videos all get updated often through Windows Store.
On the other hand, when it comes to Windows Phone 8, this becomes a different story. Apparently, all built-in apps get updated with every major OS update, which happens once in a blue moon. This is another indication that when it comes to the OS architecture, Windows Phone 8 (in its current iteration) isn’t even close to what Microsoft is trying to achieve with their ‘Windows Everywhere’ concept and sharing the same Windows kernel. So in the case of Internet Explorer 11 on Windows Phone, you won’t see it getting updated with fixes or additional HTML 5 support any time soon until there is a OS update. Now, why is this the case? Why can’t those apps (which are in a way separate from the core OS) get updated more often directly through Windows Phone Store? The bigger question is why didn’t anyone at Microsoft suggest that in their meetings?
That being said, I’ve always felt Windows Phone 8’s team didn’t have much collaboration or meetings or talks (if any) with Windows 8’s team. Both OS interfaces (at least on the modern UI side) seem to handle things differently. There is no sense of consistency when you move from Windows Phone to Windows 8. Yes, there is that familiarity feeling but once you’re knee deep you realize they’re oceans apart.
I hope there is more in store that what was released and previewed in Windows 8.1, cause that might be an indication that Windows Phone 8.1 may not meet most people’s high expectation.
Believe it or not, I think there is still hope for Windows RT to gain traction only if the following three critical points happens:
- Rebrand it to something else other than the incredibly confusing “Windows RT” name. Call it “Windows 8 Touch”, “Windows 8 Express”, “Windows 8 Tablet Edition” or simply “Windows 8” and rename the home edition to “Windows 8 Home”. Whatever the name is, it cannot be “Windows RT”.
- Remove Desktop. Yes, there is absolutely no use for it if the only thing it can run is Office in Windows RT. And since the Office suite is being developed as modern apps as we speak, it’s more reason for Desktop to be useless on Windows RT. File Explorer has been baked into Windows 8.1’s modern UI so that too is another nail in the Desktop coffin in Windows RT.
- Apps, and lots of popular apps. Without the top 10 apps that people know and expect on a tablet platform, there will be no reason for consumers to adopt Windows RT. Make sure those apps are in Windows Store.
That’s it. Consumers don’t need to know the technical definition of Windows RT to know what Windows RT is and what it enables them to do, hence rebranding it. Consumers don’t need to be confused with the presence of Desktop on a tablet when it’s mainly used for touch. And last, but no least, apps. Bring them, and buyers shall come.
One of my tasks recently was to implement bundling and minification on a ASP.NET 4.5 web application. So naturally, I started to read many articles and tutorials on how to implement it until I understood the technology and got confident on implementing it. The implementation was quite simple really and I was very happy with the progress…until I reached a brick wall.
So for anyone who is in the same boat, I feel your pain and here is what I went through:
I added the following markup for a script bundle called ‘~/scripts1’:
That didn’t make bundling and minification work. So I tried:
<script src=”<% Scripts.Render(“~/scripts1″); %>”></script>
That gave me the same result as the previous one. So after hours of researching and playing with code, I wrote the following line right in the markup without any <script> tags:
<%: Scripts.Render(“~/scripts1”) %>
It worked! I got my bundling and minification to work only when “debug=’false'”.
I hope this helps some poor soul out there. If you need more information on bundling and minification with ASP.NET 4.5, read this article.