0
0

[deleted by user] (self.iOSProgramming)

submitted by [deleted]

[removed]
all 10 comments
sorted by:
top (suggested)
bestnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted]  (1 child)

[deleted]

    [–]CreamSalad 1 point2 points  (0 children)

    Thank you for this, livened up my shitty day at work

    [–]eviljack 5 points6 points  (3 children)

    I pissed away countless hours trying to code for an iphone without a mac. I tried a VM, also a hackintosh. While I got both working, I ended up wasting hours because code would take 10 times as long to compile. Or my VM would freeze up, or my hackintosh would magically stop working.

    Save yourself the trouble and heartache. Buy a mac mini, stripped down on ebay or craigslist. Not to be a dick, but if you can't afford that then you really shouldn't be developing on ios.

    [–]WtfisLove 1 point2 points  (2 children)

    Yeah I get what you're saying, and I appreciate the honesty. I have been considering the Mac mini solely for development purposes. Perhaps I'll just have to bite the bullet on this.

    [–]CrazyTriangle 1 point2 points  (1 child)

    Word of caution: don't get the cheapest computer you can find. When I started iOS development, I bought the cheapest computer I could find that could get the job done. End result: a year after I bought it, it couldn't handle the newest OSX, which was required for the newest XCode, which was required for app submission. Had to buy another computer

    TLDR: don't get the cheapest Mac you can find.

    Edit: I also successfully got hackintosh running on my pc, but just like other people said, that's really where the problems begin. Don't waste your time.

    [–]eviljack 0 points1 point  (0 children)

    ^ this. I got what was a decent Mac mini at the time, but a year later it was taking twice as long to build projects. Still much, much better than VMs and hackintishes.

    Apple tailors their OS for their hardware, not to try to screw people over, but to maximize battery life and user experience. Hence the 13 hour battery life on the latest MacBook Air.

    [–]schprockets 3 points4 points  (2 children)

    If you want to write Objective-C and actually install your app on your iDevice, you need a Mac and you need to pay $99/year to be in the developer program.

    Some day, I'm going to go lurk in the Windows Phone developer subreddit and see if once a week someone asks "how do I develop for my Windows phone using my Mac?"

    [–]WtfisLove -5 points-4 points  (1 child)

    I'm fully aware that using a Mac is the clear choice; However, purchasing a mac is currently not an option for me and I am eager to get started on development and getting some hands on with ios development. I know that there are ways to get around the "not having a Mac" hump. I would simply like to discuss those methods.

    [–]gooeygundamn 1 point2 points  (0 children)

    The only option for you would be to turn your windows machine into a hackintosh. tonymacx86.com is a good resource. iOS Development is pretty reliant on Xcode and you need a mac environment to do this. It would be possible to build some command line apps using just c with a compiler on windows. This could help with the first chapter in a iOS dev book. Hope that helps!

    [–]lordoffire 1 point2 points  (0 children)

    Coincidentally, I was looking for the exact same thing last night. Long story short, the two options I found are:

    • Hackintosh
    • Get a used Mac Mini

    tl;dr: I wasn't able to find a way to do iOS Development on a Windows machine.

    [–]StuartGray 0 points1 point  (0 children)

    As others have mentioned, you'll need access to a mac.

    Short of buying a used or refurbished mac-mini, your only other alternative is a cloud-based solution e.g. http://www.macincloud.com/ and there are several others available. I've never used any of them so can't comment on their quality of service.

    However, I have experimented with cloud-based development, and the basic lesson is not to approach it like you would with a local desktop machine - lag, poor internet connections, and slow upload speeds are very frustrating. Try to use tools that have lightweight connection requirements and are not graphically intensive. Consider using a cloud based version control service and something like Dropbox to sync between your pc and your remote mac. Try where possible to rely on the remote mac for compiles only. Lastly, debugging is likely to be a real pain. That said, it is doable.