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.
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.
we are starting a new desktop project and we are evaluating adobe air as our development platform. this is because most our team are flex developers and we want to take advantage of that. but we have several question in order to decide whether or not to use air as a development platform.
How recomended is to use a bridge to
communicate with peripherals through
serial and paralell ports.How can i
communicate air application with my
system database.
There is a well known framework for
object persistence, like hibernate
??. if not, what is the best approach.?
Which are the best approach for our
applications distribution, how can we
deal with product key, product
licenses, etc. What advantage do we
have using AIR MarketPlace ?
Any help you can provide me, to point me in right direction, i will appreciates
Cheers,
system communication via NativeProcesses (since Air 2.0)
Air supports SQLite; from Air you can communicate via RPC or socktes with (for example) a JavaServer with Hibernate
Air App Licensing with Sharify
Damian
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.
My main Windows development PC, running Vista Business, is getting a little long in the tooth and I'm considering replacement. Its a dual screen setup with 24" and 19" monitors. My laptop is a reasonably new Macbook and I've been using Parallels to mount a Virtual XP system on it for some time and have been pretty impressed.
The new Mac Minis appear to have dual screen support, and I'm wondering about replacing the PC box with a fully spec'ed (4Gb Ram, 2.3Ghz processor) Mac mini and mounting Parallels VM environments for development. On the face of it this has a lot of attractions - clean development environments etc. but I'd appreciate any advice from anyone who has taken a similar approach - is it feasible and robust enough for general day to day development work?
My specific development requirements are that all my clients are predominantly PC based and over two thirds of my development work is now web based anyway. However I do have a couple of legacy Delphi 6 systems (and I'm considering a Delphi 2009 upgrade) and one .Net 1.1 Windows Mobile application. I also have a considerable number of Access/SQL Server applications I look after, all those these are generally coded directly on clients machines and the need to replicate locally is rare, it would however be useful. There's also the possibility of Win32 based development in the future, and I tend to do a lot with 3D and OpenGL technologies. For non-coding applications I also run and use Maya and Photoshop on the PC fairly regularly.
I bought an Aluminum MacBook a couple months ago, got additional ram in order to have 4 gigs and I've successfully virtualized Windows XP with 3D acceleration using VMWare Fusion. I'm currently developing web applications using PHP and Javascript, some other projects with Java and playing around a little bit with XNA 3.1, all on my MacBook .. so, If this works for me it could work for you too!
You're probably not going to want to do much graphics work through Parallels' emulated video adapter.
Has anyone tried the new OVI SDK for Symbian development?
What are your experiences?
Do you believe that it can help Nokia get more programmers building applications for Symbian based devices, or do you consider Flash Lite, Java or Python to be best choices?
As I understand it the Ovi SDK is a web based framework similar to or built on WRT. This certainly fills a niche. My worry is that it will be tied to Nokia handsets only, and won't work with the other Symbian devices.
WRT, Python, Qt+Symbian C++ seem like safer bets for cross device compatibility.