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
Related
What is the difference between Windows Phone 8.1 and Windows Phone 8.1 Silverlight?
Which Option(Project) is best suitable for new app development? Also please provide Pros and Cons of each option.
So basically silverlight is used for browser based applications, you can relate to macromedia flash, it depends of what type of app you have in mind...if you would like to have your app available on all devices I suggest you use MVVM (model, view, view model) architecture so that you are able to share most of your code.
I suggest you look into Lex.DB as for database engine for your app since it works on both desktop and mobile with the same code.
You may encounter some trouble using aync tasks in silverlight, but still there are some 3rd parties libraries which helps with that.
So basically there arent any pros and cons since they are not platform related.
I saw state and notification broker for Windows Mobile, but I can't find anything like it for Windows 8.
I found this for the older OS:
http://www.codeproject.com/Articles/32200/Own-your-phone-Taking-back-control-of-your-mobile
Didn't see anything on MSDN. Where can I start on this?
I don't care which language. I have a Nokia if it matters.
EDIT: Does this mean I can't build one?
https://dev.windowsphone.com/en-US/OEM/docs/Customization/Phone_call_SMS_filter_applications
These APIs are not exposed to third-party developers.
You can not do this unless you are a OEM. Only OEMs have this functionality enabled for them. For normal developers such API does not exist for Windows Phone. Only partners with Microsoft can download the source code or view it.
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.
I recently started doing some development in the Windows Phone 8 OS I'm pretty new on this. I was doing some searching about the fact to create an app who play any audio for some specific events/actions.
I was reading the Windows Phone API reference from Windows Phone Dev Center http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff626516%28v=vs.105%29.aspx#BKMK_Win32andCOMAPIforWindowsPhone
But it seems a little confusing to me at first glance and I have the doubt of which one of the following should I use to accomplish my task.
The .Net API for Windows Phone
Win 32 and COM API
... or the Windows Phone Runtime API
Any help would be very appreciate
It really depends what you're trying to do. If you're writing a native application or are interested in cross-compatability with Windows 8 then XAudio2 or the WinRT APIs are definitely the way to go. If you just want to play some infrequent sounds (say, when you pop up a warning dialog) from within a XAML app then I have seen a number of approaches, teh easiest of which is probably just having a MediaElement in your XAML that you use to play the audio.
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.