I am a little confused with the two apps, Windows 8 (which run only on Windows 8 OS?) and Windows Phone Apps.
Based on the marketing I heard around windows 8, I assumed an app available on Windows 8 would automatically be available on windows phone?
I am assuming this is not the case after searching around, because I see a windows app store (which I assume only includes windows 8 apps), and the windows phone.
Assuming my assumptions are correct, do you need to buy a developer licence for both windows 8 app store and windows phone store?
Is it as simple as submitting your windows 8 app that was created through windows phone, or is there additional configuration or development that needs to be done? Assuming that you don't care about resolutions or functionality.
Thanks for any clarification.
*Additional question,
Where does Windows tablets running windows RT and or non RT fall into all this? Are they windows apps I'm assuming?
Hope it helps you. As the store licences are unified (WP8 and Windows 8), the development remains different http://blogs.windows.com/windows_phone/b/wpdev/archive/2013/11/06/unifying-developer-registration-windows-and-windows-phone.aspx
Yes you are correct Both the platforms need seperate Developer Accounts one for the Windows Store Apps and one For the Windows Phone Apps..and yes both the Apps are different you have to develop both the Apps Separately and submit them to the respective market separately only then would it be available in the respective markets.
Separate Developer Accounts for the Windows Store Apps and Phone are no longer required. If you have a App Store account, you should now see that you can register up to 3 phones without a separate registration process.
IF you have a developer account, VS2013, and a windows 8 phone plugged into USB, an easy way to be guided through the process is to create a new project and select a W8 Phone sample. Specify that you want to debug using a Device (as opposed to an emulator). You will get a Device is not registered for development dialog with a link to instructions.
As mentioned in other post, things have been streamlined so W8 and W8 phone mostly overlap APIs, and you can probably use the same source, but will need build separate outputs.
Related
I am trying to develop an application which will deal with the following hardware and perform the stuff mentioned. I want to know that would it be feasible .
1)
Wi-FI
Scan for wi-fi , provide option to turn it off and on or reboot it .
2)
Bluetooth
Turn it off /on , make it discoverable if its not discoverable.
Apps
Get list of all apps that are installed and provide an option to kill them if they are running or uninstall them. The provision should also list the user the apps which he has sideloaded(need to know which all are the sideloaded apps).
Internet Connectivity
If internet is connected , check whether data is flowing or not.
Battery Status
Find all those apps which are consuming too much battery.Provide the option to uninstall them and lower the screen brightness and decrease the screen lock time
All these have to be implemented in an application that I want to develop.
I would be needing links for answers so that I can provide it in my feasibility report.
thanks
You will need to write a desktop app for this. Most of what you're looking for is completely out for a Windows 8.1 Runtime app. Windows 10 adds functionality for several of the bullet points, but in both versions you'll need a desktop app to manipulate other applications.
Universal Windows apps (aka Windows Runtime apps) run isolated and cannot generally affect the system or other apps. They can make changes only within their own context.
1 and 2: Windows 10 adds the Windows.Devices.Radios.Radio class to address your radio bullets, but this functionality is not available in Windows 8.1 Runtime apps.
3: This cannot be done from a runtime app. A desktop app can enumerate a user's apps with the Windows.Management.Deployment.PackageManager class.
4: You can query connectivity with Windows.Networking.Connectivity.NetworkInformation.GetInternetConnectionProfile
5: This is not available in a Windows 8.1 Runtime app. In Windows 10 see Windows.Devices.Power.Battery
For Windows Phone 8 I have created and published an app which creates a local-only address book (no automatic synchronization to the cloud with no data access for other apps installed on the phone) and by chance I discovered today that the system lists some apps that are capable of storing contacts in the people's hub (see screenshot). How can I achieve to get my app listed there?
Windows phone 8.1 there are two main options (in open API) for implementation of the contacts application on the Smartphone.
It all depends on your scenario.
I think you need to learn starting from here:
Implementing contact bindings in a Windows Phone 8.1
This may seem an odd question , but I'm just wondering if the process of finalising a WP8 app is different to a WP7 app.
In WP7 when I am ready to publish an app I just go into the Debug/Bin folder upload the XAP top Dev Center. However, when I do this with WP8 apps they never serve ads. Also the XAP is always called something like AppName_AnyCPU_Debug.xap compared to just AppName.xap in WP7 apps (using VS2010).
I know with Windows 8 you do something different, but is it the same in WP8?
Help is appreciated.
Yes, its same in Windows phone 8.
But dont forget to check the project for store requirements.
Here is the link for more info on Store test kit
http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh394032%28v=vs.105%29.aspx
I am not sure about windows phone 7 but in windows phone 8 *_AnyCPU_Debug.xap means that xap is targeted for any CPU architecture(x86 or ARM) currently all windows phone CPU are ARM based. and secondly _Debug means that the xap is build as debug and that is not a good idea to publish the as the xap will contain unnecessary debug symbols and effect app performance. alwasy use build mode release when every you are publishing your app.
I have to implement "in-app purchase" both for Windows 8.1 and Windows Phone 8 app. The API looks the same for both platforms, besides one method: "CurrentApp.ReportProductFulfillment" (only WP has it). However, both platforms have "CurrentApp.ReportConsumableFulfillmentAsync".
My preference is to write fully reusable code (same code) for both platforms, if possible. MSDN documentation is not clear enough, so I want to understand:
Can I use ReportConsumableFulfillmentAsync on WP instead of ReportProductFulfillment? Are they have the same functionality? (maybe they left ReportProductFulfillment for backward compatibility).
Do I have to call ReportConsumableFulfillmentAsync after buying consumable only, or after every store purchase?
Thanks!
According to MSDN ReportConsumableFulfillmentAsync is Windows Phone 8.1 API, so you cannot use it when creating Windows Phone 8 apps. Stick with ReportProductFulfillment and Windows Phone 8 apps for now, it will take some time for Windows Phone 8.1 to get on the market
Only for consumables
If your are looking or a nice in-app wrapper, take a look at this https://github.com/igorkulman/Kulman.WP8/blob/master/Kulman.WP8/Services/WindowsPhoneStoreService.cs
So, our Windows Phone developer left recently, and I primarily do Android development.
We had a question from a client about the possibility of installing our Windows Phone 8 app on a Surface Tablet. Namely, is it possible to do? As it stands, our WP8 app was not written with tablets in mind, so my question is:
Is there anything I need to do to the WP8 app to get it to install on a tablet, (should it work as-is (like Android apps do), is there some sort of flag I have to enable and then rebuild, etc.?)
As #AMR mentions, the biggest challenge will be the UI; however, depending on the device functionality being used, the "backend" may or may not be a challenge as well.
There is great guidance on the Windows Phone Dev Center about practices and techniques for building for both platforms, so depending on when the phone app was built and your former developer's awareness of the overlapping platforms, you could be in great shape or just so-so shape.
Additionally, the following resources may be of help in mapping from what you have already coded in Windows Phone 8 to what you'd do in Windows 8:
XAML controls comparison between Windows Phone 8 and Windows 8
(much will be relevant to Windows Phone 7 too)
Windows Phone 8 and Windows 8 platform comparison (shows common
APIs, storage, networking, etc.)
Lastly, the Windows Phone Runtime API documentation gives a listing
of APIs only on Phone 8 vs. APIs adopted from Windows 8.
Okay well first off yes, there will be a few things that change but nothing to serious.
HOPFULLY you have a good MVVM model. If this is the case then you should be able to just copy and paste 99.999% of your backend code right into your tablet app. There are a few things that are different but its just namespace stuff. Nothing too serious.
The Major change is going to be your UI layout and UI controls. Depending on what libs you are using you will probably have a lot of conflicts.
Your best bet is to just copy and paste your backend code in and then creating a new UI. I have tried to merge phone UIs in the paste into the tablet and its rediculous at times. I found it takes less time to just recreate it.
If you need any help you can hit me up at www.AnthonyRussell.info Maybe I can help with your transfer. Just make sure to leave your contact info.