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.
Garbage Garbage Garbage Garbage
NO. It is not possible to convert an android app to iOS using a tool. You have to develop app in iOS platform using iOS SDK. There are some cross platform SDK are available like PhoneGap there you can develop app for both android and iOS. However for an existing app cant do anything.
You cannot convert the app if it was written in Java. But here are some recommendations for the future:
For applications that include 3D graphics, I would recommend Unity
If you're looking for simpler applications, take a look at Cocos2D I don't have any experience with Cocos but it is said to be portable.
But if you're looking for native GUI widgets, I don't think there is a way to do that.
Note: The answers are for ios-android only. Unity is said to support Windows Phones soon, though.
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 an iOS developer. I'm porting an app from iOS to OSX and need some good tutorials to help me get up to speed with OSX coding. This question has been asked a few times, but all the answers reference tutorials which depend heavily on Interface Builder. I do not want to use interface builder (Please don't hijack my question by asking why I don't want to use IB). Ideally I'd like to find some tutorials that assume you already have objective-C/iOS experience.
Thanks!
Interface buildier for developing OSX is close to essential in my opinion. You are going to waste so much time setting everything up yourself in code. Just remember on iOS you have a single window, and at any one time you have a single view controller on screen (generally). On the Mac this isn't true and not only that you need to think about the menus too.
This do it all yourself mindset is great when you're learning and want to understand all the ins and outs but, it sounds like you are on a real project... I mean, you probably have a deadline. Embrace IB.
If you still want to get a kick start of using cocoa without IB then I think this should be a good read.
http://lapcatsoftware.com/blog/2007/05/16/working-without-a-nib-part-1/
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.
when I use the xcode for compiling the game what is built from unity , I notice that if I choose Unity-iPhone-simulator ,there are many errors ,after I choose the Unity-iPhone ,the project runs successfully , I want to know the reson about this . Thank you for the sharer!
Somewhat related, from Unity IOS Basics:
Can Unity-built games run in the iPhone Simulator?
A: No, but Unity iOS can build to iPad Simulator if you're using the latest SDK. However the simulator itself is not very useful for Unity because it does not simulate all inputs from iOS or properly emulate the performance you get on the iPhone/iPad. You should test out gameplay directly inside Unity using the iPhone/iPad as a remote control while it is running the Unity Remote application. Then, when you are ready to test performance and optimize the game, you publish to iOS devices.
As for why iPhone-Simulator fails, likely you are using an incorrect iPhone SDK. Try setting SDk version to 4.1.
The community at large seems to regard the Simulator builder as broken and that you should stick with native builds or using the Unity remote for testing. Some information sourced from here.
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.
This might sound a bit of the topic, but i really wanna know whether it is a good idea to learn windows phone 7 development after ios development. I am still learning ios, but of the basic stuff is covered. So I was thinking to start windows 7 development side by side.
So is it a good idea?
It should be a good idea. First, you only not learn about the partial framework of the .NET world and you are scoped with the available namespaces you will use in Windows Phone 7/8.
Once you start learning Windows Phone 7, it should be easy for you to switch to another Framework Class Library (FCL) that is Silverlight that can be use to develop applications in a web browser, then switch to WPF which is use to develop desktop applications.
You will not only start in my honest opinion with Windows Phone 7 development but you will also start learning applying design patterns just by developing simple applications to the phone. Once you are comfortable with it, it should be easy for you to apply the advance stuff when it comes to Silverlight and WPF.
Pretty much as a developer, you should not be hesitant to learn, relearn, and unlearn. This is the 21st century. Everything change so fast.
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.
I need to implement a remote management system that does the following tasks on remote devices-
1) Install Software,Firmware.
2) Install Upgrades of the Software,Firmware.
3) Monitor the state of the installed software,Firmware.
OSGi can be one of the framework to achieve this, but it only supports bundles written in Java(implementations for C/C++ are available but they are not matured). I was wondering if there are any other alternatives that can manage software written in any language.
I've seen this question come up from time to time, but I don't think there is, and I doubt there will be,especially on mobile devices. Getting an API that 'feels good' regardless of language is pretty much impossible, and you need to interface with how a particular platform handles its updates. Provisioning OSGi components is just fundamentally different than updating an iOS app.
Then again, I'd love to be proven wrong on this one;-)
maybe you could have a look on MEF (Managed Extensibility Framework). Its for dotNet development and similar to OSGi. But I am more familar to OSGi as to MEF so I cannot tell the differences. I only heard from a C# pro that they have MEF instead of OSGi ^^
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 11 years ago.
I'm planning to buy Mac just to develop Apps for iPhone (iOS) using XCode. Hence, I need to know what a decent hardware configuration to develeop with XCode.
Since I will only use it for iphone developemnt, i dont want to spend alot of money on it. But also I want to get a good hardware that will not give hard to time. hence, what apple hardware and configuration you recommend.
Thanks,,
Pretty much any apple hardware will work fine. I have both a macbook pro (2010) and an iMac (2009) that work very nicely. However a big screen is a huge help especially when designing the gui parts of an application.
I use a 2011 model MacBook Air with 4GB of RAM and runs XCode like a dream.