Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
i have an ipod touch and i'm writing an app for it (mostly for personal use, but i'll eventually put it out there for free when i'm finished).

while i'm developing it, i want to actually use it on my ipod touch and change it frequently. the question i have is, once i write an app and use xcode to put it on the ipod touch, am i gonna be able to use the ipod touch away from my computer, or does it have to be plugged in the whole time i'm using my app?

what i'm worried about is this: will i have to download my own app from the itunes store and will i have to wait till june to do this?
 
i have an ipod touch and i'm writing an app for it (mostly for personal use, but i'll eventually put it out there for free when i'm finished).

while i'm developing it, i want to actually use it on my ipod touch and change it frequently. the question i have is, once i write an app and use xcode to put it on the ipod touch, am i gonna be able to use the ipod touch away from my computer, or does it have to be plugged in the whole time i'm using my app?

what i'm worried about is this: will i have to download my own app from the itunes store and will i have to wait till june to do this?
First: When you "link" an iPod Touch or iPhone to your Xcode environment, you'll have an option in Xcode to run the application on either the simulator or your "device." If you click "device," when you build and run your app, any previous versions on the device will be removed, and the new version will be installed and launched. If you quit the application, or halt the run process in Xcode on your Mac, then the application is *still* installed on the device, and can be booted without being plugged in, and without a message from Xcode.

Second: Given the above info, you'll be able to install any apps you develop onto your device and run them at any given time. You won't have to pay for your own stuff. :)
 
i am a java developer too. i found that using the samples on the iphone dev site was a great help to get started. it seems they almost have examples of all the types of things you might want to do with the UI.

the thing i noticed is that the api is limiting in a good way. for instance, nav bars go on top, tool bars go on bottom. you first have to let go of a little control and trust that doing that will make your app feel more native.

since i'm not using the iphone, i guess i haven't had any need to integrate with phone functions.
 
Danggg! You are like me, I know Java very well with a bit of C/C++ on the side. I agree with all those that said a better programmer probably would have had better use of the Developer Program. But regardless, from what I hear, you should start out with one of those books and just read through it and learn how to code in some other languages, particularly C and Cocoa. Then create a program, and try it out!
 
Danggg! You are like me, I know Java very well with a bit of C/C++ on the side. I agree with all those that said a better programmer probably would have had better use of the Developer Program. But regardless, from what I hear, you should start out with one of those books and just read through it and learn how to code in some other languages, particularly C and Cocoa. Then create a program, and try it out!

unfortunately, i've never been good at learning from books. i can really only learn by tweaking examples and by watching others that know what they are doing. luckily, the samples provided by apple provide a great cross-section of the different types of things you would like to do with the UI and the framework.
 
Second: Given the above info, you'll be able to install any apps you develop onto your device and run them at any given time. You won't have to pay for your own stuff. :)

just for clarification-- you won't have to pay Apple a fee to install your own applications as you can put them on the device yourself, however you will have to pay Apple the $99 annual fee to join the developer program (if you've not done so already). Without that you won't have a key with which to actually sign the code so that it can run.

rob.
 
ok... i'm getting no response from my request to join the developer program. is there a less... "supported" way to get apps onto the ipod touch?
 
Not sure if it is what you are looking for, but check out Google Code University.

This is a great free resource for people that want to know more about developing software and web.
 
just for clarification-- you won't have to pay Apple a fee to install your own applications as you can put them on the device yourself, however you will have to pay Apple the $99 annual fee to join the developer program (if you've not done so already). Without that you won't have a key with which to actually sign the code so that it can run.

?? I was under the impression that you cannot even move your app to your device to test, unless you have the certificate. At least, that's what others are saying... they can only test in the sim until accepted into the $99 program.
 
?? I was under the impression that you cannot even move your app to your device to test, unless you have the certificate. At least, that's what others are saying... they can only test in the sim until accepted into the $99 program.

That is correct-- you must be accepted into the program (and pay the $99) as you need a key to sign your code.

I was answering the question "do I have to buy my own app from the itunes store" -- which is: no, but you must still pay apple $99/year for the privilege of being able to download your own application to your own iPhone or iPod Touch.

rob.
 
ok... i'm getting no response from my request to join the developer program. is there a less... "supported" way to get apps onto the ipod touch?

My understanding is that there is a significant queue to get into the program, and that they are (possibly) being handled first come, first served... and that they're still working through the first day of sign-ups (at least many people who have signed up on day 1 are still waiting).

As far as a less supported way, you can always jail break your device and use the free tool chain, although this will require (possibly significant) changes when the new firmware is released as APIs have changed.

rob.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.