7 posts in this topic

Microsoft may be preparing to kill off its Windows Phone back button in a future 8.1 release. Windows watcher Paul Thurrott claims that a single source has indicated the requirement for a hardware back button will be dropped with Windows Phone 8.1, an update expected to debut in early 2014. The back button typically lets users navigate back to other applications, but Windows Phone users are said to largely use the Start button to navigate home and select other apps.

 

Windows Phone also uses the back button to access a multitasking user interface, but it's not clear exactly how multitasking will operate in Windows Phone 8.1 if the button is removed. Windows Phone 8.1 is said to include multitasking improvements for background processes and notifications. Notification support on Windows Phone has been rather lacking, and the company is widely expected to be preparing a Notification Center for the 8.1 update.

 

Other improvements include support for up to 10-inch displays. Microsoft is currently preparing a General Distribution Release 3 of Windows Phone 8, known as GDR3, that will include support for 5- and 6-inch displays. Windows Phone 8.1 is said to go a step further, extending that support to 7- and 10-inch displays. Windows 8 and Windows RT typically fill the 7-inch onwards gap, and it's not clear how Microsoft plans to encourage OEMs to use either operating system for various devices.

 

Microsoft is also said to be preparing a universal binary for applications, allowing developers to create a single app that can run on Windows RT and Windows Phone. Windows chief Terry Myerson has previously hinted at a merge of the Windows Phone and Windows RT platforms, and it appears 8.1 will push down that path. Microsoft is expected to release Windows Phone 8.1 to existing devices in spring 2014, alongside a Windows 8.1 GDR update.

 

http://www.theverge.com/2013/10/9/4820022/windows-phone-8-1-kill-back-button-10-inch-display-support-rumors

Share this post


Link to post
Share on other sites

That would imply that the home screen will support landscape in 8.1, but not GDR3?

 

Does this mean the exact same binaries will run on RT & WP8.1, as the same compiled entity? So the same app UI could theoretically be available for Windows 8.1 also? 

Share this post


Link to post
Share on other sites

So basically, what Microsoft is doing is scrapping WinRT, and replacing the tablets with WP8.1? I like this.

Share this post


Link to post
Share on other sites

That would imply that the home screen will support landscape in 8.1, but not GDR3?

Does this mean the exact same binaries will run on RT & WP8.1, as the same compiled entity? So the same app UI could theoretically be available for Windows 8.1 also?

they will probably have you write xaml for small screen,and xaml for big screen, in the same binary. so when you load it,it will choose which ui to show based on screen size.

So basically, what Microsoft is doing is scrapping WinRT, and replacing the tablets with WP8.1? I like this.

it wouldn't be scrapping RT. Phone is already a stripped down RT with phone relevant APIs. It would be adding the phone APIs and services to RT, and allowing the UI to be determined by screen size.

Share this post


Link to post
Share on other sites

As far as the API thing, it's not going to be 100% the same between WP and Windows RT with 8.1 but as far as % goes with WP8 the APIs between the two are around 35% compatible.   But with WP 8.1 they'll be around 77% compatible, big difference but not exactly code once and run anywhere quite yet.   I expect them to hit 100% with the version after though.

Share this post


Link to post
Share on other sites

I would miss the back button on the phone, made programming easier and allowed more real estate for UI instead of always presenting a back button.

Share this post


Link to post
Share on other sites

I would miss the back button on the phone, made programming easier and allowed more real estate for UI instead of always presenting a back button.

 

I don't know if they'll get rid of it tbh, it makes little sense to do so with all the apps out right now that use it so much.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.