I am newbie to windows platform.
I have few questions mentioned below.
What's diff between Windows 8 metro style app and the Windows 8 mobile app?
What diff languages I can use to develop windows mobile app?
The answers to above questions will quickstart my windows mobile development.
Waiting for your responses.
They are basically the same except for some API that are available for phone only
Windows Phone 8 now shares a common core with Windows 8. This means you can expect to write apps for one and easily port it to the other, with UI retooling of course. Developers targeting both should use C#/VB + XAML and JS for apps, and C++/D3D for games.
VB/C# + XAML, C++ + DirectX (for complex graphics), JS can be used Windows 8 surface but not with phone (got this from jump start to windows 8)
Related
I'm working on a port of my WP 8.1 app to run on tablets, and PCs. I started working on a Windows 10 port, but I realized that it won't run on Windows Phone 8.1 devices. As far as I know the other way was to create a Universal 8.1 app, but that would mean to redesign most of my pages, there would be a bunch of API and control incompatibility with WP and Windows 8.1. (Pivot control does not exist in Windows 8.1). That's why I chose the easier way to port to UWP. The question is: can I upload a Windows Phone 8.1 package, and a Windows 10 package (only PC and tablet device families targeted) to the same app in dev center? So both mobile and PCs, tablets are supported.
Yes, you can upload (say) a Windows Phone 7 Silverlight package, and a Windows 10 universal package. Devices will get the highest version numbered package that will work for their device
I want to develop a windows 8 metro app (C# and XAML) which support the bluetooth low energy(BLE) feature. I found a sample Windows Phone app for this.I tried to convert to Windows 8 app, but some features are not supporting in Windows 8 like Windows.Devices.Bluetooth.BluetoothLEDevice . Is there any Windows 8 application for BLE? Please help me.
Please see the link: Windows phone app for BLE
https://code.msdn.microsoft.com/windowsapps/Bluetooth-LE-Explorer-91669105
If I make a Windows8 App (Javascript template), will I be able to compile it also for Windows Phone 8 and as windowed Windows 7 application?
No.
WinJS (or any other format) Metro Store apps do not have a direct equivalent in Windows 7.
For Windows Phone 8 you may be able to reuse some of your business logic but you'll need a new UI layer and the WinJS functionality isn't supported.
I'm wondering how to develop an app for both Windows Phone 8 and a Windows 8 tablet? When creating a new Windows Phone project in Visual Studio, I don't see any options to target phone and tablet devices like in Xcode. Are there any guidelines or tutorials on how to create the same app for both devices?
As mentioned you need to create two separate projects.
It is possible to create a library called Portable Class Library where you can put code that can be shared between a Windows Phone 8 app and a Windows Store app. See Maximize code reuse between Windows Phone 8 and Windows 8
Another technique mentioned in the article is to use MVVM to be able to separate UI (which differs more between platforms) from logic (which is easier to share).
Although they are using the same core, Windows 8 (RT) and Windows Phone 8 are distinct operating systems. This is different that iPhone/iPad which both run iOS.
You will need to create individual projects for Windows Phone 8 and Windows RT. If you are coding in C#/XAML, the code should be fairly portable between the two platforms. Here is a good session from the Build conference on how to leverage your code across Windows 8 and Windows Phone 8.
I am new to Windows Phone applications and Windows 8 Apps. All I know about windows 8 is the metro style and the news that it will run on the PCs, tablets and Phones as well.
I want to get started developing an App for an expected Windows 8 Phone Device. All the guideline I found for windows 8 is for developing the apps for windows 8 tablets or PCs (not phones). Here is a link for windows 8 SDK, I am looking at.
Should I start developing a regular windows 8 app (for tablet) assuming that it will run on the expected upcoming windows 8 phone device?
Does anyone have any idea?
Microsoft has made very few announcements so far on the developer story for Windows Phone 8. What little news has been announced can be viewed in the Windows Phone Summit video here:
http://channel9.msdn.com/Events/Windows-Phone/Summit
The only statement made so far regarding development across the two platforms is that applications developed using C# and Xaml will have "high compatibility" between Windows Phone 8 and Windows 8.
Windows Phone 8 is due out later this year so hopefully development tools aren't far off. If you want to get started right away I recommend you try your hand at developing a Windows 8 application using C# and Xaml. That should catch you up to speed and get you prepared for Windows Phone 8.
You can get started at http://dev.windows.com
I think there is nothing really official about the development of applications windows phone 8 (except as regards the integration of the new features of future devices). Everything in internet indicates that one of the reasons that drove microsoft to update wp7 is precisely the desire to converge development for windows 8 with development for windows phone8. This convergence will be visual (for example the pivot layout will be characterized by a single page horizontally scrollable similar to windows 8 apps) and under the hood (with a kernel very similar).
The enhanced hardware will perform more complex operations (thus tending toward user experience similar to pc).
What we also know that in some metro style app in actual microsoft store someone found comments in the source related to the integration of the app in windows phone 8.
What I can suggest then is to develop your app for windows 8. In all likelihood make the porting to Windows phone 8 will be simple (different sized images for backgrounds, different icons, but side code probably will not change anything).