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.
Related
i wanna test my game that uses google play services api(for realtime multiplayer). But i don´t have an android phone or tablet, i only use the emulator.
Is there a specific model of phone that i should buy to use google play services or will it work on any android device?
On emulators, there´s a "target name" called google APIS, so i was wondering about the device.
I have already made my game work on emulators, but even of ButtonClicker example, there´s a delay on the timer on one of the emulators and not on the other. Maybe i should try with a real device?
It will work on any Android phone (not Android compatible). Avoid devices like the Kindle Fire that are compatible, but not actually Android. If it has the Google Play app and it's running Ice Cream Sandwich or higher, you should be set.
The Nexus devices tend to be developer favorites, as they have no customization from carriers or manufacturers and are fairly cheap. Developer Editions would be a good alternative.
As far as I understand, Microsoft wants to allow "having both desktop and modern ui GUIs" only available for web browsers (am I mistaken here ?).
Does that mean common apps will be developped twice ? With e.g Skype being available both as pure desktop app and pure modern ui app ? And if a user installs both, these both instances will share no data ?
I can't imagine them doing a shift towards gesture friendly uis/hybrid ui, and leaving full blown desktop apps (not toy/phone-like/game apps, that can live in one space only) with no integration/entry points inside modern ui. Or maybe they want to participate in that "kill full-blown desktop apps" movement ?
So is there a model for a desktop app developped in whatever GUI toolkit, that wants to have some minimal integration with a small HTML/CSS/JS frontend in modern ui, like for e.g providing a dashboard of favorite or recently accessed files, contacts, etc ?
Your first statement of "only in a browser" is not correct. Desktop applications don't change their current design paradigms. You can have browser-based apps on the desktop, of course. But full clients are still supported and still viable as a real solution to problems.
Your takeaway from that comment should be that desktop applications are not deprecated as people assert. The reality is, desktop applications are still the only solutions to many problems.
Your second question of shared data is not correct. Skype shares lots of data with its app companion. Not because of shared local storage, however; it is because of the services that it shares. My account and contacts are on the server. So, they share a lot.
Your takeaway from that comment should be that Windows 8 apps should not highly leverage local storage but should be built as service-oriented clients. To that end, your desktop applications should have already started to leverage this architecture, too.
Your third question (which is very cryptic) seems to be asking if a desktop application and a companion Windows 8 app can share or integrate with each other. The answer is yes. Not only can they share the same service, but file associates, custom protocols, and some of the non-Store manifest capabilities allow for this explicitly. Line of business applications should have a companion app, if you ask me. The integration points are many - though not every. But there is no other way to leverage the new capabilities of Windows 8 without introducing a companion app - even if that app does very little.
Your takeaway from that comment should be that Windows desktop applications and companion Windows apps are the preferred and anticipated development approach.
Best of luck, thanks for the question.
I want to develop some small apps for personal use. I don't want to market them, nor I want anyone other but me to have them. As a developer, I want to be able to put some minor utility app I'd like to have on my own smartphone (an iPhone, of course).
As I'm not going to develop anything commercial in the near future, I'm not going to subscribe the developer program. Is it possible to develop personal apps without subscribing to Apple's program? Would jailbreak help? Am I going to miss any possibility in the development (ability to subscribe to servers, message, use the maps...)
Thanks
there's a number of threads of this.. they all use ldid and are normally jailbroken
How can I deploy an iPhone application from Xcode to a real iPhone device?
Attempting to deploy my app on my jailbroken iphone, but the app closes immediately!
I know this is repeated question. I read almost all the threads , googled a lot and became more confused. I read Microsoft Mobile Internet Toolkit (MMIT) is not used anymore and Windows Mobile 6.5 Developer Tool Kit is widely used .
Requirement:Develope and publish websites for mobile phones.
Envoirnment:VS2008/.net 3.5
I am new to mobile web application development. I want to know how to start ,what are the frameworks i should know/download,sample websites or articles..
Thanks,
Vanitha
If you want to create web applications for mobile devices using microsoft technologies check out this site:
http://www.asp.net/mobile
It has simple how-to.....
If you're going to invest in a new skill, I'd focus on iPhone and Android development - they're far more widespread than windows mobile.
I'm trying to understand the relationship between the Intel Atom Developer Program (IADP) and the new OS called MeeGo.
IADP let's me create applications that run on both MeeGo as well as Windows devices, as long as the device is based on the Atom processor. The IADP apps are published in an app store called AppUp, which is very much like the Apple App Store.
The MeeGo operating system merges Intel's Moblin and Nokia's Maemo into one OS. The purpose seems to be to make it possible to develop software that will run on Intel powered devices, Nokia-made devices, as well devices from other companies. Nokia has its Ovi Store that will support MeeGo apps.
With its OS independent runtime, the question is what an IADP app really is? Is an IADP app a beast of its own, or is it just a MeeGo app that has been restricted to run only on Atom powered devices?
Will it be possible to recompile my IADP app to run on all MeeGo devices? Sold in Ovi Store?
Intel and Nokia have me really confused. Where should I go as a developer?
If you really have to decide now, go qt.
There are a lot of important decicions yet to be made. Last week on embedded systems Nürnberg, I spoke to both parties about meego, and even they have been preparing the merger behind close doors, very few people inside both companies were involved so far. No wonder developers are clueless at the moment. You are not the only one beeing confused.
I have been developing for atom but never with iadp and start developing with maemo. Qt is a save bet for developers because it is not only for Intel and Maemo, but used heavily in every major hardware platform so far. I decided to be happy about every advantage the MeeGo merger gives me and go with the progress of details being sorted out.
My guess: Don't wait for selling IADP apps in OVI store.