IDE, build tools, emulator... things that i must pay for them without any choice to replace?
You can use Carbide C++ IDE and Qt SDK and Symbian SDKs, all of which are free.
http://developer.symbian.org/wiki/index.php/Category:Symbian_Signed :
In terms of cost if you plan to deploy
your application commercially you will
need a Publisher ID which costs $200
per year and each time you sign a SIS
file it will cost €10 using Express
Signed and €150 if you use Certified
Signed.
https://publish.ovi.com/info/ :
Ovi Store will sell your app, giving you 70% of the revenue. Registering as a publisher on Ovi Store will cost 50 €.
So, besically, you can get development tools for free, but distributing your app will cost if it is a commercial application.
These are all free. You have to pay for signing your application at the end for distributing
Related
I have a computer with Windows 8 Enterprise (Evaluation) and an Intel Q8300 CPU (which does not support SLAT as far as I know).
I also own a Samsung ATIV S - Windows Phone 8 smartphone.
I would like to develop Windows Phone 8 app(s) but the emulator won't run on my PC. What are my options? Can I plug the phone via the USB cable and debug the app on it? Or this will also require a developer account (which I hear is 100 US dollars per year)?
You have to unlock your phone to debug applications on it, and yes, you need a Windows Phone Developer account to do that. It costs 100$ per year.
MSDN: About deploying and running apps on a Windows Phone device
You have to meet the following prerequisites before you can deploy an
app to a Windows Phone device:
You must be a registered developer. For info about registering as a developer, see Registration info.
The phone must be registered. For more info, see How to register your phone for development.
And about Dev Account cost: Register for a Dev Center account
An annual Dev Center subscription is $99 USD plus any applicable tax.
For that, you’ll get to submit unlimited paid apps to Windows Phone
Store. You can also submit up to 100 free apps.
You do not need to pay for Windows Phone Developer account. All you need is a computer with Zune software running and a USB cable. The rest is mostly automated.
Depending on your app, if you can get 99% working on f.e. android, it might be an option to upload a winphone build to the Windows Phone Store and specify its a beta submission. To do this, yes, you need a developer account. But you dont need to unlock your phone.
Add yourself (and other devs) to the beta tester list and submit the app.
It will be available in ~1 hour, but it doesnt really appear in the store; you need to install it using a link sent to you by mail.
As for debugging, try Weinre.
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.
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.
I seem to end up evaluating a lot of software. This requires me to constantly install all kinds of things on my system. It creates a huge clutter and I spend a lot of time during the install process, and if I don't like it, then removing everything I've done. Much of my evaluation tends away from the features of the software being evaluated and toward how difficult it is to install. I'm sure I miss good software which may have actually been a better choice, because of this startup cost.
With the advent of VM software like VMWare Player and VirtualBox, it would be much easier to sell someone like me your software, if you just provided an image that I could load into the VM and run. I'd be looking at the features almost immediately rather than fighting with which revision of whatever. The VM would take care of all of this for me.
Am I missing something, or should vendors and OSS start distributing VMs for their wares?
Most of my evaluations are for server side software installed on Linux, so OS licensing is not the issue.
VMs require that the operating system have a valid license key. For free operating systems this wouldn't be an issue, but if you're developing for something like Windows machines, each time they send out a demo version of their software, they're sending out a license key that they would have to pay for.
This would be incredibly expensive for most companies.
The only downside I would say IMHO is the size of the images, if say you have a 20 MB application, do you really want to download/transfer an entire OS just for that application.
I would say a better approach would be to have a ready to go VM and then you simply take a snapshot (on Virtual Box, I assume similar feature exist in other players)
Then simply install the applciation inside your sandbox environment, and then just Zap it when done (i.e. return to your Snapshot)
Darknight
This can be done for softwre that runs on open source platforms, and VMware have a library of images which do just this (though the images that are used for evaluating commercial software is generally for infrastructure-type things that have very, very complex installation requirements):
http://www.vmware.com/appliances/
However, if the software is for the Windows platform, you don't really have the opportunity to do this, as Microsoft's Windows licensing would prevent it. Unless, you're Microsoft, of course, in which case you can in fact do this - and MS has done this to permit easier evaluation of such software as Visual Studio, SQL, and many others:
http://technet.microsoft.com/en-us/bb738372.aspx?ppud=4
Novell has an appliance builder called Suse Studio that lets you pick the software you want, it builds out a VM with the software (and dependencies, etc) for you. You can then try out the VM, download it, etc.
Whether the software you're looking for is available or not is a different matter.
Disclaimer: I work for Novell (though not with the Suse team)
But yes, if you can deal with the OS licensing issues, or possibly host trial environments yourself, this is a very effective way for a vendor to demo their app. The problem is that all vendors don't always have the infrastructure (or lack the awareness) to do so.
Microsoft provides fully-provisioned VM's for time-limited trials of their software. So if you want to trial select Microsoft products in that manner, you can do that today.
There is no sign, though, that Microsoft will make this available to third party Windows software vendors.
In the SaaS (Software-as-a-Service) world, you can get fully-provisioned virtual servers that include Windows and your software of interest on a pay-as-you-go basis, based on both Linux and Windows. For example, see Amazon Web Services
For windows, you may be better off developing a portable application that runs from a usb key. That is how Embarcadero distribute All Access. I received a 4 gb usb key that contained multiple applications. Most could be run straight from the key without installation. I believe Embarcadero will be licensing the technology at some stage.
If you are using a programming language such as Delphi or C++ with little in the way of external dependencies, a portable application is straight forward to develop. For .net, it is much harder, but can be done with Mono, or something like Virtual Application Studio.