I'm currently trying to know if I can release a couple of my games on Windows Store. The games are single-file executables and they do not require any additional software installed nor installation. More to say, they performed very well on Steam.
I don't plan to use in-app purchases or ads. The games support any screen resolution and both mouse and touch input and fullscreen mode.
So is there a way to publish a "not-Visual-Studio" app on Windows Store?
I have found this thread on Windows Dev Center but not sure if the guy succeed with his trial and it seems he was talking about releasing air app, not a standalone .EXE .
Any help?
Adobe Air is not a way you can create a windows store app. There is a windows desktop bridge for converting .net apps to windows store apps. There is an ios bridge to convert apps created objective c to windows store apps. There is also a way to convert web apps to windows store apps. I am not aware of any way to convert an adobe app air to a windows store app.
Related
I have read many articles about the "forward compatibility" of WP apps stating an app targeting 8.0 can run on an 8.1 phone. But I have not verified this on WP Store.
I have published a universal app for WP 8.1 and some users have installed this app. Now I am investigating the various upgrading scenarios happen when Windows 10 Mobile comes out later this year.
Scenario 1: Can a user download and install the 8.1 app with a newly purchased Windows 10 phone? Will it show up in the new, unified Windows Store?
Scenario 2: Can a user who has already installed this app continue to receive updates to this app after he upgrade his phone to Windows 10 Mobile? I have no plan for a Win 10 release at this stage and I will update the 8.1 release in the months to come.
It will be helpful if you can provide me some links about the policies of the new, unified Windows Store.
Yes to both. Existing apps will show up and can be installed from the store. As with the existing stores, users will get the most relevant app for their device. Your existing Windows Phone 8.1 apps will run on and be available for Windows 10 mobile devices. You can update it and expect your users to receive the updates.
This is discussed in the store sessions from Build:
All That is New in the Windows Store and Store: Deep Dive on Publishing Universal Windows Apps
The blog entry Get ready for the Unified Dev Center dashboard preview and upcoming Store changes goes into detail on what you need to do to support various scenarios with the updated store.
At this link: http://blogs.msdn.com/b/windowsazure/archive/2013/01/09/new-windows-azure-mobile-services-getting-started-content.aspx I see that there are separate Azure SDKs for Windows Store and
Windows Phone 8.
In my app suite (a Windows Store app and a complementary WP8 app), I'm currently using only the
Windows Store SDK - I haven't downloaded/installed the WP8-specific Azure SDK. Do I need to?
It's the same download for WP8 and Windows 8; of course, iOS is completely different, hence the calling out of different SDKs.
Can I use Adobe AIR to create applications using Javascript and the Web Audio API and then have said applications still retain their audio functionality after they are turned into stand alone desktop/mobile applications. I have not started using Adobe AIR yet so I am not acquainted with the software.
I don't think AIR's runtime includes Web Audio support; it may on iOS, if the user has iOS6 installed; won't have it on Android right now, and doubtful they keep it synced with current Chromium on desktop.
I realize it's been asked countless times whether iPhone apps can be built in Windows and that the simple answer is no, with workarounds such as using VM or even something like Dragon SDK which requires the app to be written in C/C++, but I would like to build an app using Objective C.
My question is can the code for an iPhone app not be developed on a Windows computer, uploaded to a remote Mac computer, compiled on the Mac, and then downloaded back to Windows to install via iTunes? I don't want to buy a Mac mini to get my feet wet with iPhone development, but I don't want to be limited to writing an HTML 5 app using Phone Gap or similar.
If nothing else, wouldn't it be possible to develop the app directly on a remote / virtual Mac using a remote desktop connection?
If either of these are possible, does anyone know of a company offering such a service? If not, what would be a likely reason that it hasn't been created? It seems like there would be enormous demand.
Perhaps http://www.macincloud.com/ is what you are looking for.
I believe what you're trying to do is not possible but how about MonoTouch ?
http://xamarin.com/monotouch
Using .NET on Windows technologies to develop iPhone and other apps ?
at first i thought with Titanium, i can develop for Mobile and Desktop over AIR on Desktop only, but a quick look at the AIR Site, i guess i am wrong.
Benefit from a consistent, flexible,
and visual development environment for
applications on multiple platforms and
devices such as smartphones,
smartbooks, tablets, netbooks, and
PCs.
so my question is are there any major differences of titanium over air that i shld be aware of?
if no, i guess now air maybe better documented and has the backing of a more recognized company? after working with titanium desktop for a while i felt abit helpless and the docs are not really helping much
There are a lot of subtle differences, of course, and there are advantages and disadvantages to working in either, but the largest difference is that Titanium can produce apps for the iPhone/iPad, and AIR can't (well, at least not conveniently).
AIR can produce iPhone apps that you can deploy using the ad-hoc provisioning, but you can't distribute via the app store.
I've got desktop apps on both and am making a mobile app right now. Titanium desktop will cut your dev time to 1/3 of the time you'll take jumping through AIRs various sandboxes and security measures. Best yet, the code I wrote for my Ti desktop app is all javascript with about 3 Ti API calls and can be taken anywhere. The AIR app is all mangled by the wild structure you have to use with AIR apps and 1 million api calls.
The downside to Ti desktop is the API isn't as fully featured, and the Ti team pushes 4 times as many updates for the mobile API as the desktop API. Also, you won't be able to port your app from desktop to mobile easily as they are two different structures and APIs.
That said, developing for iPhone and Android on Ti is the same exact process and that won't happen on AIR.
Lots to weigh, but for my money it's Ti over AIR.
Hope this helps.