Microsoft again caught in awkward transition - how does this keep happening?

[FinancialP]

It all depends on the apps. The reason most people use the browser to access "web apps" on desktop is because they are full featured and can be windowed/tabbed easily. Where as apps generally lack both.

With Windows 10, you can Window those apps. The only question is the features which is the devs own problem.

I'd much prefer to use dedicated apps that integrate with other apps and the OS than a browser IF I know that half way through using the app, I won't have to open a browser anyways to access specific functionality.

People build desktop apps for OSX even though it has less than 5% market share. So why can't the same be said for the opposite. Especially if you can write once and execute everywhere.

Microsoft is basically building the DREAM environment for almost all app developers. iOS meanwhile is still a pain in the *** to develop for. But magically all developers will ignore Windows 10 and stick with iOS cuz iPadz!!!

I'm tired of this doom and gloom attitude towards anything Microsoft. They could solve world hunger and people would still find ways to ***** about it or claim they didn't do it.

Don't know why you're so angry, but I can't help you with that.

I didn't say anything about doom and gloom, I just posted a casual statement.

OSX app development is laughable just as the Windows Store. People rarely use them, if ever.

I don't know why your brought iOS into this either. What does "iPadz" mean?

 

[dezzilak]

The problem here isn't Microsoft, it's that weird carrier-operator-phone maker relationship in the US. Locked networks like the ones Verizon and Sprint operate don't exist in Europe so you can basically use every phone on every network. And while exclusive deals do sometimes exist they're rare and short lived.

Take the Lumia Icon for example, available everywhere outside the US as Lumia 930 on every network out there. It came a bit later than the Icon but it's widely available now.

Make it pentaband, like the 1520.3? And sell it outright from your website. Damn, that reminds me of some also big company...

 

[Mike Gibson]

And companies like Adobe are already shifting their apps to be touch friendly, as they continue, what's stopping them from recompiling for ARM?

Are the Adobe programs WinRT or Win32? Touch-friendly != WinRT. I can use the Win32 touch APIs to get smooth panning, zooming, drawing, etc.

 

[Mike Gibson]

Well, WP won't exist with Windows 10. Windows 10 will be just Windows 10. Any apps developed for the Windows 10 store will be on WP. If Windows 10 can surpass Windows 8 in success, I guarantee there will be better apps.

That's not true. Devs will have to "tailor" their apps to the various screen sizes which leads to different versions for different devices (see the techrepublic.com interview). Plus, using phone-specific APIs will throw exceptions (which is stupid from an OS API viewpoint).

MSFT threw away all of their decades of Win32 effort, and decades of ISV Win32 effort, when they created WinRT. As expected, it failed miserably and will continue to fail ... just like any totally new mobile OS would do these days. It will turn out to be the most expensive blunder in business history (including the Nokia purchase the total must be around $10B already and that's not counting the unknown billions of $$$ of lost Win32 users in the future).

 

[spaulagain]

That's not true. Devs will have to "tailor" their apps to the various screen sizes which leads to different versions for different devices (see the techrepublic.com interview). Plus, using phone-specific APIs will throw exceptions (which is stupid from an OS API viewpoint).

MSFT threw away all of their decades of Win32 effort, and decades of ISV Win32 effort, when they created WinRT. As expected, it failed miserably and will continue to fail ... just like any totally new mobile OS would do these days. It will turn out to be the most expensive blunder in business history (including the Nokia purchase the total must be around $10B already and that's not counting the unknown billions of $$$ of lost Win32 users in the future).

Tweaking the UI is not that big a deal for most apps. It's just like building a Responsive website which basically every legit sire/company has done. 90% of the code is the same, just some code to tweak the UI on top.

Also, they've also said that they will provide tools sets that will automatically scale the UI if the app uses standard controls, etc.

It's clear you just have a vendetta.

 

[spaulagain]

Are the Adobe programs WinRT or Win32? Touch-friendly != WinRT. I can use the Win32 touch APIs to get smooth panning, zooming, drawing, etc.

No, but they've already created Photoshop Express which is WinRT, iOS, and Android. It has basic functionality but can be expanded.

WinRT is very flexible as far as languages are concerned. From my understanding the main issue with it currently is the clusterfvck APIs.

Man, you really hate WinRT.

 

[tgp]

Tweaking the UI is not that big a deal for most apps. It's just like building a Responsive website which basically every legit sire/company has done. 90% of the code is the same, just some code to tweak the UI on top.

Do we know how much tweaking will be involved? And who uses apps on desktop machines (full Windows)? So far the browser or legacy apps are much better than Store apps on the PC; the Store apps don't give a very good user experience. If apps aren't used much on PCs, is the perceived added market actually worth anything? Will making the apps available on both machines be worth it?

These are questions that will be answered only after Windows 10 is on the market.

 

[spaulagain]

Do we know how much tweaking will be involved? And who uses apps on desktop machines (full Windows)? So far the browser or legacy apps are much better than Store apps on the PC; the Store apps don't give a very good user experience. If apps aren't used much on PCs, is the perceived added market actually worth anything? Will making the apps available on both machines be worth it?

These are questions that will be answered only after Windows 10 is on the market.

Agreed. But if what MS is saying is true, then there really is no other option. I mean they are designing the ultimate development platform for the "modern" world of apps and development. If that doesn't work, nothing will.

I just don't see how it could get any better than Windows 10. We know the open environment like Win32 has serious draw backs in security and quality control. Sure devs have full access to build on the PC, but that means they can also really fvck your computer up. I understand legacy developers don't like the idea, my Dad is one of them. But lagged out computers and viruses is part of what gave Windows a bad name. Siloed environments with a full portfolio of APIs is a much better approach kong term. Especially from an end user experience perspective. Developers just need to get over it. Obviously they can because they have with iOS which is probably the most restricted and siloed app environment ever.

 

[spaulagain]

Do we know how much tweaking will be involved? And who uses apps on desktop machines (full Windows)? So far the browser or legacy apps are much better than Store apps on the PC; the Store apps don't give a very good user experience. If apps aren't used much on PCs, is the perceived added market actually worth anything? Will making the apps available on both machines be worth it?

These are questions that will be answered only after Windows 10 is on the market.

As far as tweaking is concerned, it's hard to say. But I've built multiple Responsive websites and web apps, its really not that big a deal. In fact it's kind of fun. I'd say it adds maybe 10% more work on top of just a standard desktop UI. And maybe less once you create a set of standard code like MS will be doing for apps.

The thing is, tweaking the UI is inevitable. Screens sizes are almost infinite in sizes and resolutions now. If developers can't handle adapting the UI appropriately for these various screen sizes, then they shouldn't be building apps in the first place.

 

[fatclue_98]

Can we leave APIs and tweaking alone and get back to MS bashing and gloom and doom? It's so much more fun.

 

[tgp]

The thing is, tweaking the UI is inevitable. Screens sizes are almost infinite in sizes and resolutions now. If developers can handle adapting the UI appropriately for these various screen sizes, then they shouldn't be building apps in the first place.

Yes, of course tweaking is inevitable. iOS and Android developers do it some for tablets. I still question though how much value the combined market of PCs and mobile will be. It seems that apps aren't used much on PCs, so will developers consider them as added potential customers? They will need to exceed the user experience of the web & legacy apps. That won't be easy.

Sent from whatever device I happen to be using today using Tapatalk

 

[spaulagain]

Yes, of course tweaking is inevitable. iOS and Android developers do it some for tablets. I still question though how much value the combined market of PCs and mobile will be. It seems that apps aren't used much on PCs, so will developers consider them as added potential customers? They will need to exceed the user experience of the web & legacy apps. That won't be easy.

Sent from whatever device I happen to be using today using Tapatalk

If you can build a website with all the features, you can build an app. Websites are not an easy platform to develop on. In fact, with high functionality web apps, web technologies are a pain in the ***. They're document format being forced into an application tool.

But you know why developers build applications on the web? Because of accessibility.

The same would apply to Windows 10. If Windows 10 is available on desktops, tablets, phones, TVs, watches, cars, refrigerators, etc. that's massive accessibility which equals huge opportunity for devs.

I'm not saying that the day Windows 10 launches, magically all these apps will appear, and be full featured. Obviously it will take sometime, especially as W10 builds a user base. But the potential/opportunity is the highest Microsoft has ever provided. And really any platform ever. Even iOS and Android are still very limited in opportunity. They're Tablets and Phones only. But Android is working on watch and car OS versions.

My overall point is that if W10 doesn't provide the fix for Microsoft's dilemma, then nothing will.

Also, if Cortana is available across all these devices. Think how devs can use that to their advantage. Again, the clear advantage apps have over websites is the access they have to the OS APIs and other apps. Cortana is a huge part of that API integration.

And don't forget all those websites you guys are talking about are using technology that Microsoft has given a front row seat to in their WinRT environment. You can build a 100% HTML/CSS/JS WinRT app and at the same time have access to the OS APIs. That's awesome for web developers.

 

[tgp]

But you know why developers build applications on the web? Because of accessibility.

Yup. And building applications on the web gives access to every device that has a browser, including Macs, iDevices, Androids, and everything else. Windows devices are about 1/3 of all devices, so putting it on the web triples the market.

 

[spaulagain]

Yup. And building applications on the web gives access to every device that has a browser, including Macs, iDevices, Androids, and everything else. Windows devices are about 1/3 of all devices, so putting it on the web triples the market.

But it also limits functionality especially in regard to OS integration and cross app communication.

I'm a web developer and a big proponent of web technology. I love it. But I also know its limitations.

If the web is so great than we should all ditch our fancy PCs and MacBooks and just go buy Chromebooks.

Applications are still the more powerful and effective way to provide a service and optimized UI to the end user. And they will be for a long time unless the web fundamentally changes how it works.

Devs clearly still find use in developing apps, otherwise this app gap between WP and Android/iOS would be non-existent and irrelevant.

Developing for the web will always have the best accessibility but it comes at great costs.

 

[Mike Gibson]

No, but they've already created Photoshop Express which is WinRT, iOS, and Android. It has basic functionality but can be expanded.

As far as I can tell, the "touch" announcement was about adding touch to their existing Win32 programs.

WinRT is very flexible as far as languages are concerned. From my understanding the main issue with it currently is the clusterfvck APIs.

Win32 already supported every language ever invented.

Man, you really hate WinRT.

Yes. I hate that MSFT screwed up even simple/trivial things like file access in WinRT. It is the worst performing API I've ever seen. The people who designed it should be ashamed of the results (I bet it doesn't show up on many resumes).

I'm an MSFT shareholder and a Windows-only ISV. MSFT's idiotic decision to kill Win32 will hurt me both personally (because their stock will crash within five years) and professionally (fewer Windows users to buy my programs). I have a WP8 program out there but its total sales for 1.5 years is equal to about two days of my Win32 program sales.

All they had to do was create a scalable UI API on top of their existing portable OS, Windows, and backport it to Win7. I could have used it in all of my programs and it would have covered all of my current and future customers' systems.

I had hoped with Win10 that MSFT would kill off WinRT refocus on Win32 ... but they're still blowing the "Universal app" horn. Plus they're apparently going fragment WinRT yet again (we'll have WinRT80, WinRT81, WinRT10, WinPRT80, WinPRT81, WinPRT10?). It takes forever to get a new version of WinPRT out in the field so I can't convert my WinPRT80 app to WinPRT81 yet and who knows when there will be a significant WinPRT10 userbase to work with. I may not be a good businessman but I'm not stupid enough to create and maintain three separate code trees to support a system with almost zero interested users. That time would be better spent learning iOS and Android, which I've heard aren't pretty for development (which proves that easy-to-develop-for doesn't mean that a platform will lure developers).

 

[spaulagain]

As far as I can tell, the "touch" announcement was about adding touch to their existing Win32 programs.


Win32 already supported every language ever invented.


Yes. I hate that MSFT screwed up even simple/trivial things like file access in WinRT. It is the worst performing API I've ever seen. The people who designed it should be ashamed of the results (I bet it doesn't show up on many resumes).

I'm an MSFT shareholder and a Windows-only ISV. MSFT's idiotic decision to kill Win32 will hurt me both personally (because their stock will crash within five years) and professionally (fewer Windows users to buy my programs). I have a WP8 program out there but its total sales for 1.5 years is equal to about two days of my Win32 program sales.

All they had to do was create a scalable UI API on top of their existing portable OS, Windows, and backport it to Win7. I could have used it in all of my programs and it would have covered all of my current and future customers' systems.

Why the hell would they kill WinRT? Yes it got off to a rough start because MS was still crossing threads when they launched it. But like I said earlier its a much better platform going forward.


It gives every development platform equal play (HTML/CSS) and creates a much more secure app environment which is much better for the end user. It also allows for better communication between applications and doesn't take 8 hours to install an application.

I understand you're frustration but you can't honestly expect them to have kept Win32 forever. Especially when it creates problems that had plagued Windows for years.

And are the other platforms any better? Apple applications can't even be installed on a desktop if its an iOS app and visa Vera. And Apple just announced a new proprietary app develop language for iOS apps. And should I even bring up Android? What a fvcking cluster fvck. Try to build apps for that and see how many different version of the apps you have to build then.

Sounds to me like you just can't handle the idea of technology changing and having to adapt. Well, I have news for you, that's the nature of technology. MS can't avoid it forever. Its why they fell behind, because they stuck with the old for so long to please people like you.

Even as a web developer I'm having to learn new technologies and refactor websites all the time. That's just a fact of industry.

 

[Mike Gibson]

Why the hell would they kill WinRT? Yes it got off to a rough start because MS was still crossing threads when they launched it. But like I said earlier its a much better platform going forward.

It wasn't just a rough start and the disaster has continued. It was designed to fail.

I understand you're frustration but you can't honestly expect them to have kept Win32 forever. Especially when it creates problems that had plagued Windows for years.

I expected MSFT to only do what was required to make their platform succeed in the device spaces and that was to add a simple, scalable UI API and framework. Not throw away all previous developer experience with a new system that started with zero users and zero backwards compatibility. It was a recipe for failure ... and guess what, it failed miserably.

BTW, you do realize that your precious WinRT API and framework is just a layer on top of Win32, correct? All the goofy file access APIs eventually call into the Win32 file and directory APIs, the internet access APIs call into Win32's WinInet and WinSock, etc.

And are the other platforms any better? Apple applications can't even be installed on a desktop if its an iOS app and visa Vera. And Apple just announced a new proprietary app develop language for iOS apps. And should I even bring up Android? What a fvcking cluster fvck. Try to build apps for that and see how many different version of the apps you have to build then.

And yet, with all those warts and problems, those platforms are massively successful. Proof that an ultra-new, super-hip so-called "Modern" API and framework was not necessary to create a successful platform for devs or users.

Sounds to me like you just can't handle the idea of technology changing and having to adapt. Well, I have news for you, that's the nature of technology.

That's the familiar technological failure response, "we were too advanced for you numb nuts". I guess the Office division at MSFT also can't handle the idea of technology changing seeing as they have yet to convert their programs to WinRT ... and they're the equivalent to a multibillion dollar company with thousands of employees.

MS can't avoid it forever. Its why they fell behind, because they stuck with the old for so long to please people like you.

No, MSFT is behind because they couldn't create a consumer-oriented ecosystem like Apple (iPod, iPhone) and Google (search, Gmail, etc.). Windows and Win32 had nothing to do with it and, in fact, was used by their competitors when building their empires.

Edit: MSFT made the same mistake 25 years ago with OS/2. It deviated significantly from the popular Win16 API and it failed. The correct way to make a transition was shown in the Win16 to Win32 transition, where you almost just needed to recompile to see significant benefits.

 

[awilliams1701]

Am I the only one that thinks that photoshop and video editing requires dual monitors of 24" or bigger with 1080p or better? In other words a desktop

 

[spaulagain]

Am I the only one that thinks that photoshop and video editing requires dual monitors of 24" or bigger with 1080p or better? In other words a desktop

It doesn't require it, it just makes it easier. But when I'm on site for photography (I do motorsports), it's very nice to have a portable device to do that kind of post processing right there.

For example, I went to Petit Le Mans a couple weeks ago. And each night in the hotel I loaded my images on to my Surface and began post processing work. But then when I get home I do any additional processing needed and organize the files.

The point is, it's not a "this or that" scenario. You guys are looking at this as a black and white issue. It's not, and that's the whole point of Windows 10, to adapt the UI to how it's being used at that time.

It is literally the EXACT same concept as responsive websites. One code set that simply adapts to the given device/use case. Sometimes I need to view a web app on my phone, other times on my laptop/desktop at home. Either way, the website tweaks the UI to fit those uses cases.

I don't understand why people don't get this. Especially when there a million examples around them.

 

[spaulagain]

Do you guys know how a responsive website works? If not, look it up, maybe that will help you understand what they are doing. Responsive websites are all one code set. With CSS making small tweaks to the UI at various screen size break points via media queries. When it comes to development, its really pretty easy once you get the hang of it. And it makes for a fantastic user experience for the site visitors.

The great thing about it is a mobile layout for a responsive website even applies to desktop. On a desktop you cam shrink the browser to as small as 300px if you want. If the website is responsive, the layout will adapt according. Makes for great flexibility even on desktop!