Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

A MacBook lover

Suspended
Original poster
May 22, 2009
2,011
4,581
D.C.
Hey all, two questions!

1) Are there any developers taking advantage of this new "In-App SMS" that was announced for 4.0. If so who/where so I can see progress?

2) I am really interested in making apps. I know that it may require a lot of dedication to do so, but if someone could point me in the direction of a good guide, maybe some source codes of iphone apps to help me learn, that'd be amazing. I run windows so windows-only coding applications. My goal is to make nice shiny apps. I am a beginner at coding.
 
You have to have a mac to run xcode (the program used to create iPhone apps).
 
Dang, isn't there a way to run a virtual machine though?

Also what exactly is an API and how long does it take to design an app around it.
 
Dang, isn't there a way to run a virtual machine though?

Also what exactly is an API and how long does it take to design an app around it.


Based on those questions you have a VERY long way to go! There are ways to run OSX in a virtual machine, however I wouldn't recommend it. The performance is downright poor; it's also a violation of the EULA.

Think of API's as code that is already put together for you to use specific features, whether they be hardware or software. For instance your earlier post about in-app messaging, that is an API that you call with a few lines of code - without having to manually code, the sometimes, thousands of lines of code yourself.
 
Dang, isn't there a way to run a virtual machine though?

Also what exactly is an API and how long does it take to design an app around it.

An Application Programming Interface (API) is an interface implemented by a software program to enable its interaction with other software. It is similar to the way the user interface facilitates interaction between humans and computers. APIs are implemented by applications, libraries and operating systems to determine the vocabulary and calling conventions. The programmer should employ it to use their services. It may include specifications for routines, data structures, object classes, and protocols used to communicate between the consumer and implementer of the API
Taken from Wikipedia. I would also advise not trying to emulate OS X is Windows, it will cause all sorts of issues.
 
Based on those questions you have a VERY long way to go! There are ways to run OSX in a virtual machine, however I wouldn't recommend it. The performance is downright poor; it's also a violation of the EULA.

Think of API's as code that is already put together for you to use specific features, whether they be hardware or software. For instance your earlier post about in-app messaging, that is an API that you call with a few lines of code - without having to manually code, the sometimes, thousands of lines of code yourself.

Very informative, thank you.

Probably one of my favorite In-app SMS was this one: Tlert
TlertWeb4.png


There are alot of in-app sms apps when you jailbreak but this one is just amazing. Any chance of a port or simular app now that this API is available?
 
Very informative, thank you.

Probably one of my favorite In-app SMS was this one: Tlert
TlertWeb4.png


There are alot of in-app sms apps when you jailbreak but this one is just amazing. Any chance of a port or simular app now that this API is available?

You're misunderstanding what in-app SMS is. I wish it was what you're talking about. iRealQuickSMS was wonderful when I used it.

The API that's included in 4.0 allows apps to send SMS' without having to exit and switch to the SMS app like how you're presently allowed to send emails from other apps without being redirected to the Mail app.
 
I suppose that's nice if you have an app like shapewriter. What would what I was talking about be called, why exactly would such an excellent feature not be integrated?
 
I suppose that's nice if you have an app like shapewriter. What would what I was talking about be called, why exactly would such an excellent feature not be integrated?

Its not allowed by Apple.
It will only work on that particular app alone if it had it integrated.
It wont be like that with every app your in.
Like wether you use youtube or you're in settings or using Safari.
Something like that can only be done with a JB iphone currently.
 
Hey all, two questions!

1) Are there any developers taking advantage of this new "In-App SMS" that was announced for 4.0. If so who/where so I can see progress?

a. Probably a few thousand. b. Google Blog Search is probably your best best. Some developers just can't keep their mouths shut.

2) I am really interested in making apps. I know that it may require a lot of dedication to do so, but if someone could point me in the direction of a good guide, maybe some source codes of iphone apps to help me learn, that'd be amazing. I run windows so windows-only coding applications. My goal is to make nice shiny apps. I am a beginner at coding.

a. Learn to program.
b. Learn to program in Objective-C.
c. Get a Mac
d. Sign-up for the $99 iPhone Developer Program
e. Learn Cocoa Touch
f. Write app
g. Profit! (perhaps)

You need to consider, however, just where the app market is in 5 years or so, when you have completed these steps. ;)
 
a. Learn to program.
b. Learn to program in Objective-C.
c. Get a Mac
d. Sign-up for the $99 iPhone Developer Program
e. Learn Cocoa Touch
f. Write app
g. Profit! (perhaps)

You need to consider, however, just where the app market is in 5 years or so, when you have completed these steps. ;)

I mainly agree, but not fully: You don't need a Mac, you can often install Mac OS X on your PC. You should also move step d) behind step f). You can even debug the apps on your device without paying for the dev program preemptively. And: I don't think you need 5 years to complete the steps, more like 2 years.
 
I mainly agree, but not fully: You don't need a Mac, you can often install Mac OS X on your PC.
picard-facepalm2.jpg


Often? Also, I really doubt someone asking the sort of questions the OP is, would find installing OS X on a PC a simple process!

OP: Buy a Mac, buy some books and get reading! Good luck :)
 
a. Learn to program.
b. Learn to program in Objective-C.
c. Get a Mac
d. Sign-up for the $99 iPhone Developer Program
e. Learn Cocoa Touch
f. Write app
g. Profit! (perhaps)
Here's my recommended order:
a. Learn to program.
b. Get a Mac
c. Learn to program in Objective-C.
d. Learn Cocoa Touch
e. Sign-up for the $99 iPhone Developer Program
f. Write app
g. Profit! (perhaps)
If you have to get a Mac anyways, you might as well learn Objective-C and Cocoa Touch on it. Just easier that way. And you'll probably want to see your app running on an actual device fairly soon. It just feels more real that way. For that you'll need to have singed up for the paid program, in order to access the Provisioning Portal to get your certificates, etc. all set up.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.