Hi, i learned c++ and im planning on buying a macbook pro to make iphone apps. I have a lot of questions.
1.Do i need to learn the basics of objective c before i start making apps for the app store.
2.When i learn the basics what next?
3.Have you guys actually made money selling apps in the app store.....how much.....how long did it take you to make that app?
4.what are some good tutorials....?????
Please be aware of this before you continue: THE APP STORE IS NO LONGER A BUCKET FULL OF MONEY, WAITING FOR DEVELOPERS TO COME AND GET IT.
OK, that aside, here are my suggestions. Learn JavaScript. Believe it or not, it can really help you learn Objective-C (codecadamey.com). Then I would learn Java (there are some courses that I used on iTunes U).
After that, learn Objective-C (not Cocoa - once you learn Objective-C, you pretty much know Cocoa, save for a few APIs). THEN learn Cocoa, and THEN learn Cocoa Touch. Master each one BEFORE you move on. That is what worked best for me.
Now, think about this before you invasion millions of $ coming your way, I had an app featured by Apple on the Mac App Store - and I made just a little over $3,000 in one month. It may be different for iOS, however.
Also, marketing is key. Just releasing an app won't help you. You have to take every step possible to get a successful app. There are some good books that I like, particularly a book with a grapefruit on it by APRESS (at least that is the publisher, and can't find it online right now - or in my house ).
Hi, i learned c++ and im planning on buying a macbook pro to make iphone apps. I have a lot of questions.
1.Do i need to learn the basics of objective c before i start making apps for the app store.
2.When i learn the basics what next?
3.Have you guys actually made money selling apps in the app store.....how much.....how long did it take you to make that app?
4.what are some good tutorials....?????
thanks
Objective c isn't a huge leap from C++ IMO. In fact, a lot of apps are built with C++, so depending on what you want to do, the amount of Objective C you would have to learn could be minimal. So I'd recommend going straight into it.
As for money issue, I'd recommend doing something else if that's the sole reason you want to make iPhone apps. The days of a making an app in a week and having it sell millions are over. Expect to put long hours and a lot of investment in before getting something back. And even then, no guarantees.
Learn JavaScript. Believe it or not, it can really help you learn Objective-C (codecadamey.com). Then I would learn Java (there are some courses that I used on iTunes U).
After that, learn Objective-C (not Cocoa - once you learn Objective-C, you pretty much know Cocoa, save for a few APIs). THEN learn Cocoa, and THEN learn Cocoa Touch. Master each one BEFORE you move on. That is what worked best for me.
Wow, I honestly couldn't agree less.
My day job is working on a hybrid app (lots of Obj-C/Cocoa Touch, lots of JavaScript). JavaScript and Objective-C are nothing at all alike. I also don't agree about the Java comment, although that's at least less of a stretch.
And finally, learning Objective-C will get you zero percent of the way to learning Cocoa and/or Cocoa Touch. Obviously it is very important to learn Objective-C if Cocoa/Cocoa Touch is ever to make any sense. But to suggest that you're most of the way there after learning Objective-C is just wrong. All knowing Objective-C will do is help make the Cocoa/Cocoa Touch documentation more approachable.
Plus I'd suggest just learning Cocoa Touch, not desktop Cocoa first, if the goal is to write iOS apps. Cocoa Touch is both a subset and superset of Cocoa; once you know Cocoa Touch you know all the Cocoa you need for iOS development.
__________________ Recall It!Tag your notes. Tag your photos. Tag your thoughts. Tag your life.
Learn JavaScript. Believe it or not, it can really help you learn Objective-C (codecadamey.com). Then I would learn Java (there are some courses that I used on iTunes U).
After that, learn Objective-C (not Cocoa - once you learn Objective-C, you pretty much know Cocoa, save for a few APIs). THEN learn Cocoa, and THEN learn Cocoa Touch. Master each one BEFORE you move on. That is what worked best for me.
Wow, I honestly couldn't agree less.
My day job is working on a hybrid app (lots of Obj-C/Cocoa Touch, lots of JavaScript). JavaScript and Objective-C are nothing at all alike. I also don't agree about the Java comment, although that's at least less of a stretch.
And finally, learning Objective-C will get you zero percent of the way to learning Cocoa and/or Cocoa Touch. Obviously it is very important to learn Objective-C if Cocoa/Cocoa Touch is ever to make any sense. But to suggest that you're most of the way there after learning Objective-C is just wrong. All knowing Objective-C will do is help make the Cocoa/Cocoa Touch documentation more approachable.
Plus I'd suggest just learning Cocoa Touch, not desktop Cocoa first, if the goal is to write iOS apps. Cocoa Touch is both a subset and superset of Cocoa; once you know Cocoa Touch you know all the Cocoa you need for iOS development.
I agree with dljeffery in disagreeing with padsoftware, on all counts. Objective C is not a huge language. It takes some study and practice to get the hang of it, but it's easier than C++.
The iOS frameworks are another story. They are very large, and very rich. I honestly think they are too much for any one human being to know completely. You get comfortable with the basics, learn how to use the documentation, and then learn new frameworks and features as you need them. At some point the light turns on and it learning new APIs becomes pretty easy. Apple is very consistent with their style and design, and their frameworks are well written for ease of use.
I do agree with padsoftware about the app store, though. These days, releasing a good app to the store is not enough. You have to do market research first, promote it to your target audience and solicit and incorporate their feedback while you are developing it, and then aggressively market it once it's released if you expect to make any money on it. If you just write apps and release them, you'll be lucky to sell a few hundred copies.
Our company is doing more consulting work and less speculative development these days, although we still do some of both.
Check out this password generator app that shows various techniques including using a data container singleton object to share data between objects in your project.
My day job is working on a hybrid app (lots of Obj-C/Cocoa Touch, lots of JavaScript). JavaScript and Objective-C are nothing at all alike. I also don't agree about the Java comment, although that's at least less of a stretch.
And finally, learning Objective-C will get you zero percent of the way to learning Cocoa and/or Cocoa Touch. Obviously it is very important to learn Objective-C if Cocoa/Cocoa Touch is ever to make any sense. But to suggest that you're most of the way there after learning Objective-C is just wrong. All knowing Objective-C will do is help make the Cocoa/Cocoa Touch documentation more approachable.
Plus I'd suggest just learning Cocoa Touch, not desktop Cocoa first, if the goal is to write iOS apps. Cocoa Touch is both a subset and superset of Cocoa; once you know Cocoa Touch you know all the Cocoa you need for iOS development.
It should be noted that I am mainly a Mac app developer, and not an iOS app developer, so that could make a difference.
Java helps with learning objective-oriented languages. Although they may be very little alike, learning Java first can make is easier in learning Objective-C and Cocoa.
Java helps with learning objective-oriented languages. Although they may be very little alike, learning Java first can make is easier in learning Objective-C and Cocoa.
Possibly, although most likely just due to the fact that once you've learned one programming language, the next is going to be easier to learn than the first.
__________________ Recall It!Tag your notes. Tag your photos. Tag your thoughts. Tag your life.
It should be noted that I am mainly a Mac app developer, and not an iOS app developer, so that could make a difference.
Java helps with learning objective-oriented languages. Although they may be very little alike, learning Java first can make is easier in learning Objective-C and Cocoa.
My background is as a Mac developer also, but I still disagree with you. Javascript? Really? Why?!?
As for learning Java first: Java is a C-like object-oriented language that's easier than C++.
If I remember correctly, the OP said he had experience with C++, so learning Java first would not be very useful. I jokingly call Java C+-. It's sort of like watered-down C++, minus the operator overloading, pointers, and some other C++ constructs.
Even if you don't have any programming languages, learning Java and/or Javascript first seems like an awful lot of work fore not a lot of benefit.
If I had to pick a language to learn before Objective C that would teach you object-oriented concepts, it would be Smalltalk. That is the granddaddy of object-oriented languages, and Objective C is closer to Smalltalk in some ways than the other commonly used object-oriented languages.
Check out this password generator app that shows various techniques including using a data container singleton object to share data between objects in your project.
It should be noted that I am mainly a Mac app developer, and not an iOS app developer, so that could make a difference.
Java helps with learning objective-oriented languages. Although they may be very little alike, learning Java first can make is easier in learning Objective-C and Cocoa.
Why not jump into objective C? It's not that big of a stretch from Java & objective C. Besides, the OP knows C++. I'm pretty sure he gets the hang of programming.
To the OP, buy yourself a iOS 5 book. It'll lay the basics out for you.
objective c
It may be different for iOS, however. 
Linear Mode
