As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I have started to build my own apps on iPhone and iPad using the iPhone SDK. The next question that is always asked by the client is, "Can we have it on Android?"
So my question to you, 'the internet', is: what are my options?
I don't have the time to learn another language (learning iOS has been enough!), so are there companies who specialize in this, or are there any online services that do a conversion?
Any help on this welcome, just need to know which way to turn...
No, there is no way to convert an existing iOS app to an Android app.
However, there are cross-platform frameworks that allow you to code once and deploy your app in more than one platform. The most popular are based on HTML/CSS/JavaScript and one of them is PhoneGap.
You can also develop for iOS and Android with Adobe technologies such as Adobe AIR (this was forbidden by Apple until recently).
And there are online services (such as Mobile Roadie) that allow you to generate cross-platform apps using a content management system.
That said, I strongly recommend to:
Learn Android and Java development if you want to specialize in mobile development.
Take advantage of the strengths of each platform when working on an iOS/Android project, instead of creating something that uses only what's common to both.
Converting a native application from one mobile platform to the other is not a straight-forward process unless the initial application was built with a framework with cross-platform capabilities from the start.
Your options at this point are learn the other platform and develop it yourself, or contract with another development company which specializes in the platform you need to target.
Due to the massive differences between the 2 platforms, you are looking at a complete rewrite of your application. You either do it yourself or pay someone else to do it. I don't see any shortcuts you can take.
You may be interested in reading my book, HTML5 for iOS and Android, which enables you to take web apps created in HTML, JavaScript & CSS, and turn them into standalone apps that you can upload to the app stores (for free or to sell). See http://html5formobile.com - the wrappers to do this for the iOS and Android SDKs are freely available on the website, and you don't need any knowledge of either programming language if you follow the instructions in the book.
You can try the following https://bitbucket.org/zabirauf/icona.
Its open source iOS to Android Application Conversion Tool.
Even if there was a way to easily port an Objective-C application to Java, I wouldn't highly encourage it. iPhone users and Android users are two different families of users. The typical iPhone interface just wouldn't sit well with Android users who aren't familiar with how the iPhone works. Yes, I understand that the UIs of both iPhone and Android seem pretty trivial to learn to most people, but when you break a novice's comfort zone, it puts your applications (or websites) on a higher learning curve.
You should take the time to learn Android's language and UI and develop your application in a fashion that is consistent with how applications on Android work. As said in other answers, if your taught yourself Objective-C, you should find that Java will come pretty easily to you. In addition, in never hurts to know more than one programming language.
You can't just convert iOS apps into Android. iOS is Objective-C and Android is Java.
I highly doubt there are 'converters' on the internet, even if there are that's not the way you should program an app because every SDK has his own special capabilities and you should use them for maximum user-experience.
I'm sure there are some companies who specialize in porting apps from iOS to Android. Look it up on Google I'd say..
If you want an easy place to look for android development you can try appMaker which I hear is a GUI based Android development tool or I believe Google has released its own GUI based android application development tool. If you are not a java programmer than you might be better off with the gui. Otherwise I would say android is not too different from traditional java. As a java programmer who went from Android to iOS, I will tell you Android is a walk in the park compared to learning iOS. Two completely different beasts in my opinion.
Selecting a mobile development environment which will enable you write once and deploy/distribute it on many devices would be a better solution in the future. If your application is HTML-based, go with HTML5/CSS alternative (ex: PhoneGap, ). If you prefer native, then chances are you may want to learn Lua, a scripting language (ex: Gideros Studio) or C++ (ex: Mosync).
Other than that, the application you created on iOS with Objective-C is very, very hard to port to Android and other devices.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am a .NET developer (more than 6 years now) and just starting to learn about mobile/smartphone/tablets development. Logically, I (and probably everybody else out there) would like the application we create to run on all smartphone platforms. It just feels natural from the normal user (layman) perspective that if it's a "mobile app" it should run on mobile device. It shouldn't matter if I own iPhone or Android, mobile app is a mobile app. Note: I am talking about native platform development, not HTML/web apps that can be used from browsers.
So this is just a high-level overview question... what are the current strategies (in year 2013) to deal with this issue? The way I imagine mobile cross platform development works is there's probably a single common code base that implements app's business logic and then for each targeting platform we need to develop GUI part separately. How far is this from truth in practice?
Take for example the popular game "Angry Birds". I played it on iPhone, Android and even from Chrome browser on Windows Desktop (probably as Flash or HTML5 game) and each version had pretty much identical feeling when played. How did they do that? I imagine they have game engine as common code but in what language could it be written? As far as I know there is no common programming language that given the single source code files it can be compiled into native binaries for ios/android/win8 phone.
Unfortunately, there is no way to develop a cross-platform app which has really native look and feel and shares same code for all platforms.
Its possible to share some code on some platforms though (for example, you can use C/C++ for iOS and Android), but only for the logic part of your app. To get native UI you will be forced to use native APIs. If your app doesn't involve some complicated data processing then this approach may have more downsides than really helping you out.
You can get rather good platform independence with hybrid app platforms such as PhoneGap or Titanium, but that involves HTML/Javascript development which could lead to a lot of time and efforts required to bring user experience to be somewhat similar to that of a native app.
Since you are a .NET Dev one logical solution for you would be to use Xamarin's offerings. (http://xamarin.com/) They allow you to develop your back-end logic once and then compile it into all three major mobile platforms (iPhone/Android/WP). You can then use this back-end logic project to write the UI layer for each specific platform.
Another option that devs have is to use the javascript/html route similar to PhoneGap. While I haven't looked at this recently there used to be some performance hits and hardware usability gaps when going the JS/HTML route. This may have been improved now.
EDIT:
Since you specifically mentioned games like Angry Birds. The Unity platform offers very good support for development that is compatible with most devices if you need 3D.
For Angry Birds specifically...they use Box2D for the Physics and I'm not 100%, but it looks like Cocos2d to draw the elements.
If you are looking to build games and like the idea of Xamarin then take a look at MonoGame which basically looks like an XNA port to the Mono Framework.
in addition of Jared's answer, this afternoon I tested Xamarin.
You are a .Net Developer and if you are already using Visual Studio, you are so lucky. Because Xamarin has an extension for Visual Studio
I just want to give a bad impression about xamarin, you can test good ones by the time, user interface is created in a xml based file and there is no auto complete, so you have to write whole code or use properties window. But I think it will be better by the time. nice coding
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm looking at ways to use Ruby for mobile cross-platform development. We need support for at least Android en iOS, with Windows Phone and Blackberry support as nice to have. It'll be an app that will end up in the app stores for the general public, so it's not an enterprisey in-house only thing. So far I've found:
Rhodes, covers all the platforms mentioned and open source. We don't need the extra (paid) functionality from RhoMobile right now
RubyMotion; iOS only and costs 199 dolla, unfortunately there's no trial version available
Ruboto, Android only and open source
MobiRuby, iOS only with Android support planned, open source, but looks like it's not mature enough at the time of writing for our needs
We also have a must-have use case in which we need access both the camera and the accelerometer simultaneously and draw data from the accelerometer on screen. Because this is so specific, it's not supported in any cross-platform framework I've looked at (including others like Phonegap, Titanium, etc) and it looks like I'll need to write native code for each platform to get this working.
So far I'm inclined to choose Rhodes. It's a proven framework and seems to be able to do everything I need, including 'going native' for the aforementioned use case. Another option would be to use both RubyMotion and Ruboto, which are both solutions to write Ruby instead of Objective-C or Java. In theory I should be able to share common code (like connectivity and storage) across platforms, although I couldn't find any examples of anybody successfully using these two for writing an app that works on both Android and iOS.
I'm wondering if somebody can confirm my thinking or that I've overlooked something. Any additional insights are welcome of course.
If you choose Ruboto, you can use your UI-independent Ruby code as is. The UI code will most likely be platform-dependent anyway.
Ruboto is still young, but there are more projects starting to use it. One example is
https://play.google.com/store/apps/details?id=com.jonsoft.globalchat
It shares the communication Ruby code across platforms.
being one of the developers on the Ruboto project, I can promise you good support and the full Ruby experience.
For iOS RubyMotion looks good, but I have not used it. You should be able to use a shared code base for common logic, but separate code bases for the UI and for accessing sensors.
I would go ahead and use native Java for Android and RubyMotion for iOS and have two code bases. RubyMotion is the most stable of the ones you mentioned and worth it for iOS development, but there isn't a good alternative on the Android platform.
Rhodes has nothing do with web apps. Rhodes allows you to build native apps with Ruby and is many years more mature than those alternatives. It also supports every major smartphone OS
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As we are still in the design stage we have no code in place yet for our mobile app. I then stumbled on the PhoneGap tool which has left us thinking. We are both from a Java background so that is why developing using ADT/Java looked like the only option. Is the knowledge ramp up for PhoneGap steep or do you think it would be worth going with it from the start seeing as we have no existing code done yet.
We had intended to use GAE/Big table for our back end persistence. Is this still possible if you use PhoneGap for the front end?
Also, can I assume it's possible to use Selenium to automate functional tests with phoneGap?
Our UI will just consist of Buttons, a sprinkling of static images and Text. Am I correct in saying the the performance drawbacks of PhoneGap should probably not be an issue in this case?
I did develop both for both platform but they are completely apps and below notes are based on my experiences, I am writing for PhoneGap (I think) and you can assume android is the opposite side.
Cross platform, right now it is supporting all major phones (Android, IOS, WP) I am not sure it is case for you as you only tagged for Android.
HTML5, JS, CSS these are my area as you are Java based developers so it is up to you.
Not native so will be slower than native.
Cross browser compatibility. I think this does not need explanation especially for desktop browsers it a pain the mobiles are more easier but it is still a problem.
To answer your questions,
Yes you can use GAE/Big table for backend, with AJAX as PhoneGap uses file:// protocol it is supporting cross URL request.
I personally don t use PhoneGap, if the app is a game and have lots of animation going on. But in your case it is a application for listing data and responsive web might make your life easier than native app to support all screen size.
I have no idea about Selenium testing so I keep my silence for that.
And shorter answer to your for me YES you can use and should.
Hope this helps.
Lets get going to answer your bunch of questions ?
Would I prefer you to use PhoneGap ?
Definitely Yes, The learning curve is not steep too , All you have to know is basic HTML,CSS and Javascript. Since you have also mentioned the app is simple,It would be good to use PhoneGap. Everybody know that PhoneGap sucks at Performance but since your app seems simple it wont be a problem.
Why did I recommend ?
Write once, deploy across lot of mobile platforms (If you want to support more devices)
Can Selenium Tests be run ?
Yes, You can,its just a web app. :)
Go for it, Give it a try.
If you want to support only Android or iOS or WP7 then I would prefer native development over PhoneGap because Performance matters.
In your case, you can choose between those two. There will be no serious drawbacks.
In many cases, particularly business applications which are connected to web services, choosing between Phonegap and native app is a matter of personal choice. I've met some people who prefer Phonegap and other people who avoid Phonegap, Appcelerator, or other wrapper frameworks and prefer native code.
Phonegap is easy to learn and if you need some functinalities beyond that provided by Phonegap, you can create a plugin for your app. That said, you still need to write native code for the plugin if you need to implement functionalities not provided by Phonegap.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I want to write simple games for mobiles, something like a good Tetris program. I want it to work on Android and iPhone phones.
My current knowledge of programming is fairly good in web development such as PHP, MySQL, HTML, CSS, JavaScript and C/C++, and Java, all intermediate level, and basic OpenFL programming.
I have the following questions:
If I code in XCode can I port/deploy it on Android phones?
What are the languages/packages I need to learn?
Can I get some helpful tutorial links to the same for a new bee?
Most of the people I know that port between iphone and android using the native tools use C++ / OpenGL ES / OpenAL and small amounts of objective-c / android NDK to handle the OS specific stuff. You want to reduce the OS specific code as much as possible as that is the code you have to rewrite for new platforms.
This can be a lot to handle if you have never done it before.
If it's your first time doing game development you may like to go down another path like Unity3d or Corona SDK. Since you want to do 2d game development Corona may be a better fit.
Both Corona and Unity3d have great forums that will help you out.
If you want to learn Objective-C, then I would suggest the Cocos2D engine for 2d game development. Again they have a great forum for asking questions.
For iPhone you will have to know Objective-C
For Android you have more choices Java should be the first one on the list.
And the of cause you could use the android-scripting framework.
Android Scripting
A Pretty interesting Project is Titanium by appcelerator.
Titanium
You can use Javascript, HTML5 and CSS3 so it might work out pretty well for you.
They furthermore have a pretty big community.
Hope this helps!
Depends what you mean by port. In general it's not a straightforward task. Both Android and iOS have OS-specific APIs which you will use. Additionally, the languages are also different (see #2). The language and platform differences will likely cause you to write your application somewhat differently.
For Android: Java. For iOS: Objective-C. As far as gaming goes, OpenGL will serve you well. You could consider using a 2D graphics library that will abstract that a bit too like libGDX, AndEngine, or Cocos2D. If you do though, be aware that if that library isn't on both platforms, you'll have an even harder time porting. Again, for each platform you'll want to look at their platform docs too. Here for Android, and on Apple's developer site for iOS.
As far as Android goes, look at the source code for Replica Island. Can't say I can recommend you a great iPhone game dev tutorial unfortunately.
The native SDK for iOS uses Objective-C, and the native SDK for Android uses Java. Most people develop native apps in those languages directly. Even if they shared the same language, the two system's work so differently under the hood that you wouldn't be able to share the code directly. In both cases however you can use C++ to do most of the graphics programming in OpenGL, so that part at least you could share directly.
There are a number of cross-platform solutions available however, allowing you to deploy both iOS and Android apps from the same codebase. For a 2D puzzle game a pretty ideal solution is Corona SDK.
A major misconception by many game developers is that it's somehow better to develop your game specifically for either iOS or Android from the start. I've been developing mobile games for years and am finding that developing portable games that run perfectly on both Android and iOS takes no longer than writing specifically for one - so long as you use one of the modern platform libraries, like BatteryTech. Porting has been a non-issue for us since we switched.
I want to answer on the second question.
Look at this post to see the Infographics that visualize what language uses every OS. I think it will be quite helpful for you.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
More and more mobile platforms are being launched and sdk's are available to developers. There are various mobile platform are available:
Android, iOS, Moblin, Windows mobile 7, RIM, symbian, bada, maemo etc.
And making of cross platform application is headache for developers. I am searching for common things across the platforms which will help to developers who want to port application to all platforms. Like what are the diff screen resolutions, input methods, open gl support etc.
please share details that you know for the any of platform.
Or are there possibilities, by writing code in html (widget type of thing) and loading it into native application.
I know about the android, in which we can add the web view into application by calling setContentView(view)
Please share the class details where we can add the html view into native application of different type of platforms that you know.
Purpose of this thread is share common details across developers. marking as community wiki.
Cross platform tools & library
XMLVM, Codename One and iSpectrum (cross compile Java code from an Android app or creating one from scratch
Phone Gap (cross platform mobile apps)
Titanium (to build native mobile and desktop apps with web technologies)
Mono Touch ( C# for iphone )
rhomobile - http://rhomobile.com/
samples are here: http://github.com/rhomobile/rhodes-system-api-samples
Sencha Touch - Sencha Touch is a HTML5 mobile app framework that allows you to develop web apps that look and feel native on Apple iOS and Google Android touchscreen devices. http://www.sencha.com/products/touch/
Corona - Iphone/Ipad / Android application cross platform library . Too awesome.
http://anscamobile.com/corona/
A guide to port existing Android app to Windows Phone 7
http://windowsphone.interoperabilitybridges.com/articles/windows-phone-7-guide-for-iphone-application-developers
Jquery MobileTouch-Optimized Web Framework for Smartphones & Tablets
My answer here covers some of the technical limitations of cross-platfrom tools but let me expand a bit:
I think that cross-platform tools have historically always been also-rans because such tools have the wrong philosophical focus.
All the selling points for cross-plaform tools are the benefits they bring to developers. They are sold on the idea that they allow the developers to write-once-run-anywhere. They are sold on the idea that they allow the developers to expand their market without learning new APIs. They are sold on the idea that they allow the developers to slash cost and time to market.
What cross-plaform tool are NOT sold on is the benefit they bring to end users.
Benefit to the end user is not a selling point because cross-platform development is seldom a benefit to the end user. The end user does not care how hard the developer had to work to bring the product to market. Nor do they care how many platforms the app can run on when they they don't use but one platform. They just care if the app does what they need it to on the hardware they need to run it on. Unless they have a specific need to run the app on many different platforms, the fact that it does brings them no value.
Conversely, the inevitable compromises of making a cross-platform API mean that all the apps created by the API will be at best B-grade on every platform. They will never be the best tool to use on each platform.
All this means that in most use cases, cross-platform tools give the end user an inferior product compared to ones made with platform specific APIs. The end user will always have a better choice.
You make money in the long run by giving end users the most useful tools. If you don't philosophically concentrate on making the end user's life easier and more productive, you are pretty much doomed from the outset. End users have lots of choices and if your tool isn't one of the best you won't make it in the market.
You should only use cross-platform tools if you think, "the users will really benefit from running this app on many different platforms." If you start out looking at cross-platform tools solely because they will make your (the developers) life easier, then you have picked them for the wrong reason and they will hurt you more than they will help.
There are several approaches to cross-platform development on mobile devices. Of course they all have limitations. No solution manages to take advantage of all the device's functionalities the way a native application can.
Re-using code
While all mobile OS don't use the same development language and API you can sometimes share some classes or logic tier code.
C++ for example can probably be re-used for an iOS application, for an Android app by using the NDK, for a Symbian app since they are developed in C++, etc.
Some solutions also offer the possibility to write the app in an other language than the one normally used by the device. The most famous (in fact the only one I know) are commercial and based on the Mono project (C# development):
MonoTouch for iPhone [ 1 ]
MonoDroid for Android (still in development)
Similar project for BlackBerry (still in development)
But I'm not sure we can really call this cross-platform development since the re-use of code is limited depending on the device :
Windows Phone 7 will not allow native code development (maybe in further updates)
AFAIK mono like project do not exist for all platforms (yet?) bada, webOS, maemo, etc.
And the UI part also stays specific to each device.
Web development
A regular answer when asking about cross-platform development for mobiles is web development. We would then need a wrapper, that will use the mobile browser, to make it look and behave like a native application. That is how some of the cross-platform framework that we will see further on work.
The rise of HTML5 brings to web development functionalities that could only be done with a native application like geolocation, off-line application, local storage.
We can found more and more frameworks to develop web application for mobiles with a native look and feel by taking advantage of the latest web standards HTML5, CSS3, Js:
Sencha Touch
JQTouch based on jQuery
JQuery Mobile framework
But HTML5 is still very young and implementation may vary from a browser to another. Most default mobile browsers use the WebKit engine (main exception being Windows mobile/phone using Internet Explorer) and even so they don't necessarily support the same functionalities. Local database is still awkward to work with and we can't be sure how it is going to implemented by the different browsers. Moreover, even with HTML5, web development is still very limited compared to a native app. You can't access contacts, camera, accelerometer, etc.
Edit: Earlier this month the W3C have delivered some warnings about the evolution of HTML5: Article from ZDNet
So it will only suit a limited category of applications.
Cross-platform frameworks
And than we have the cross-platform mobile applications frameworks. With which you can presumably develop once and deploy on different platforms. These solutions usually focus on iOS and Android and rely on the WebKit engine. They offer more interaction with the phone functionalities while developing with web technologies. The most well-known are Nitobi PhoneGap, RhoMobile Rhodes, Appcelerator Titanium. But many others are out there and don't all use the same technique like MoSync which translate your code to it's own intermediate language before compiling it for the desired platform.
[ 1 ] Remember that Apple has a special policy about apps written for their platform. They don't seem to be blocking these apps at this date but it is an information that should be taken into account.
Edit: Apple has changed this policy since September 9.
You get some commonality when deploying as a webapp (html5 as mentioned above) but for rich native apps the APIs are completely different for the various smartphones.
HTML5 may improve things somewhat but to do interesting things you need to go native.
There are 'cross platform' smartphone frameworks such as Phonegap but I've heard mostly bad things about using it for "real" work. (lots of overhead etc)
Yes, html5 is getting some attention. You should also look at this consortium & platform to come in Q4.
Not sure about the success of that project, as it sounds like a huge challenge, but here are the details:
Website:
http://www.wholesaleappcommunity.com/default.aspx
News:
http://news.google.de/news/search?aq=f&pz=1&cf=all&ned=us&hl=en&q=%22Wholesale+Applications+Community%22
WAC aims to publish its initial
specification and components of its
SDK to developers in November. This
specification will be based on W3C
standards and create a strong platform
for developing rich mobile web
applications. WAC will also provide
backwards compatibility for devices
based upon the current JIL and BONDI
specifications.
(http://www.convergedigest.com/Bandwidth/newnetworksarticle.asp?ID=31021)
.
It IS an international coalition of around 25 telecom companies that's aiming to create a platform open to all developers and selling to all mobile phone users.
(http://www.downloadsquad.com/2010/02/15/atandt-wholesale-applications-community-is-a-platform-not-an-app/)
As far as I know most of those devices are able to run this:
Java ME - the Most Ubiquitous Application Platform for Mobile Devices
I think this can serve both as good and bad example.