Subject: Mobile | February 26, 2016 - 12:04 PM | Sebastian Peak
Tagged: windows phone, Project Astoria, microsoft, developers, build 2015, Android
A smartphone is nothing without a large selection of quality apps these days, and to that end it seemed Microsoft was going to follow the BlackBerry OS 10 method (injecting life into a platform barren of software by borrowing Android apps) when they announced the "Windows Bridge for Android" last year.
(Image credit: Microsoft)
Blackberry accomplished this by adding the Amazon app store to OS 10, which gave BB users at least some of the apps an Android user has access to via Google Play. BlackBerry also provided devs tools to help them convert Android apps to run on the BB 10 OS platform, but the market share of BB OS 10 just isn’t high enough to justify many doing this.
Microsoft appeared to be headed in this direction when they introduced Project Astoria at last year’s Build conference, which was going to enable devs to bring Android apps over to the Windows mobile OS. Well, that’s over. In an update published yesterday by Kevin Gallo, Microsoft’s Director of Windows Developer Platform, this news was spun positively (of course).
“We also announced the Windows Bridge for Android (project “Astoria”) at Build last year, and some of you have asked about its status. We received a lot of feedback that having two Bridge technologies to bring code from mobile operating systems to Windows was unnecessary, and the choice between them could be confusing. We have carefully considered this feedback and decided that we would focus our efforts on the Windows Bridge for iOS and make it the single Bridge option for bringing mobile code to all Windows 10 devices, including Xbox and PCs. For those developers who spent time investigating the Android Bridge, we strongly encourage you to take a look at the iOS Bridge and Xamarin as great solutions.”
To editoralize here a bit, I will add that I own a Lumia smartphone, and in my experience Windows Phone is an innovative and extremely efficient mobile OS. However, the lack of quality apps (and the non-existent updates for those that do exist) is too great a barrier to use a Windows Phone as my primary device. It’s telling that BlackBerry's latest smartphone, the Priv, runs Android, as BlackBerry has effectively given up trying to compete with their own OS.
BlackBerry Priv, which runs the Android 5 OS (image credit: BlackBerry)
Microsoft seems unwilling to do this, but they are a software company first and foremost and that's not surprising. But as a hardware company they have struggled with portable devices, as we saw with the ill-fated Kin smartphone, and of course the Zune music player. Android is the only realistic option if you want to compete with iOS on a smartphone, but Microsoft hasn't given up on the OS just yet. As much as I like the tiled interface, I think it's time to say goodbye to this iteration of Windows Mobile.
Subject: General Tech | May 7, 2015 - 03:17 PM | Ken Addison
Tagged: podcast, video, amd, Fiji, hbm, microsoft, build 2015, DirectX 12, Intel, SSD 750, freesync, gsync, Oculus, rift
PC Perspective Podcast #348 - 05/07/2015
Join us this week as we discuss DirectX 12, New AMD GPU News, Giveaways and more!
The URL for the podcast is: http://pcper.com/podcast - Share with your friends!
- iTunes - Subscribe to the podcast directly through the Store
- RSS - Subscribe through your regular RSS reader
- MP3 - Direct download link to the MP3 file
Hosts: Ryan Shrout, Jeremy Hellstrom, Josh Walrath, and Allyn Malventano
Program length: 1:27:38
Subject: General Tech | April 30, 2015 - 06:38 PM | Scott Michaud
Tagged: windows 10, microsoft, build 2015, build 10074, BUILD
When Microsoft forked their build numbers into 100xx and 101xx lines, we predicted that they were preparing a version to release at BUILD 2015. We also predicted that it would be heavily tested and pushed to both Slow and Fast simultaneously, which would give a good entry point for developers and probably even enterprise evaluators. I was surprised when Microsoft released 10061 last week, and then updated it just two days ago (why???) with four patches, but we ended up being correct in the end.
Microsoft has just released Windows 10 build 10074 to both Fast and Slow users. Its comes with a very small list of known issues, and they are much less severe than they were in previous releases. The first issue tells developers that Developer Mode needs to be enabled in Group Policy, rather than the place in Settings that it will eventually be. The next two issues are more severe: some games cannot be played in full screen and the People app is still broken. I am not sure how wide-spread “some games” is, but they plan to patch it via Windows Update “as soon as possible”.
One major fix is that now, when certain applications that play audio are minimized, they will continue to play audio. This bug made many media players, such as a few SoundCloud apps in the Windows Store as well as Microsoft's own Music app, pretty much useless. Until 10074, you would basically need to launch them, then cover them up with other windows if you wanted more screen real-estate.
If you were a fan of Aero from Windows 7, then you will like the blurred transparency effect of Start and the taskbar. Personally, while I think it looks nice, I was never really attached to that aspect of the Windows UI. Honestly, it used to drive me nuts when it kicked me out of games to complain about how it cannot properly manage 2GB of video memory, despite running perfectly fine if I select ignore. Hopefully that will not come back with it. But, if it is here without causing any problems, it does look pretty. Also, the Start Menu can now be manually resized to better arrange your apps. It also looks like the semi-horizontal layout is a great compromise between the Start Menu and the Start Screen for desktops.
So, as we expected, this build is what happens when Microsoft picks a target and mostly cleans up all of their relevant branches into a solid release. It is still a bit buggy here and there, but it feels better than 10049, which was itself better than 10041. That said, I also upgraded my NVIDIA drivers from 349.90 to 352.63; that could have something to do with it (although I am using the same Intel drivers).
There has not been too many announcements regarding features that are not present in 10074 though. It makes you wonder, at least a bit, how much will be added to the 101xx path until the OS finally launches.
Subject: General Tech | April 28, 2015 - 07:27 PM | Scott Michaud
Tagged: microsoft, windows 10, BUILD, build 2015
BUILD 2015 begins tomorrow, and I expect we'll learn the last features that Microsoft intends to add to Windows 10 at launch. The conference is targeted at software and web developers first and foremost. We might not see too much on the consumer side, but we should get under-the-hood information that will be relevant to consumers. For instances, some questions about Windows Store, WinRT, and DirectX 12 might be answered. We might even get a public DirectX 12 SDK (and more).
Note: WinRT (API) is not the same as Windows RT (OS).
As we noted earlier, development was forked into a 100xx-branch and a 101xx-branch of build numbers. We assume that, due to the proximity to the conference, the lower build number is getting polished for public presentation while the higher builds will surface later, with more experimental features.
Microsoft published an introduction video, based on the 10061 build, to introduce the new OS to new users. I guess they are expecting a new wave of testers after the conference, probably both developers and enterprise evaluators. It is brief but interesting, although it surprisingly did not mention anything about the “Continuum” interface to switch between mouse/keyboard and touch experiences.
As stated, BUILD 2015 starts tomorrow and we will probably have a bit of coverage for it.