The "correct" answer is yes. TDD should be considered "best practice" wherever the tools for TDD are available either in the language or in the framework. Even if they aren't available in a form you may be used to with Java or .NET, you can create a simple program that consists of calling each of the unit test methods one at a time, catching thrown exceptions (which indicate a test failure).
The reason why is that cheap, inexpensive little in-house prototype apps, built as proof-of-concepts or for training/demo/personal use purposes, become production apps all the time. Just as an example, I had at one point a job duty to create bootable flash drives for our field techs, containing system tools and OS images. After doing it manually the first time for a batch of 50, I created a simple app, ThumbPrinter (being clever), that automated a large portion of the script-running and batch-tracking, and all I had to do was tell it how many thumb drives I wanted made, where the data to put on them was, and which drive letters would be used during the batch, and then handle the plugging in and unplugging of flash drives as it went.
That app is now used by others in my department and I'm constantly called on to "fix" things that were never a problem when I just used the program myself, because unlike in a production environment, I knew how I'd use it and never considered using it in any different way, and I also knew the causes of certain glitches and how to avoid them because that was easier than making the code work right. If I'd known the app would be used by anyone else I'd probably have taken more care building it, up to and including TDDing it.
Now, that being said, TDD is not necessarily the end-all be-all of proper software development. We got along for 3-plus decades before it was ever proposed, and people still write correct code without unit tests. So, it's really up to you; you'll have to find out just how easy it will or won't be to write and run unit tests for an iOS app, and whether that cost of time and effort is worth the advantages of TDD (regression prevention, YAGNI adherence, definition of "done" and automated proof of correctness).