a 'finish test' button, or something like it, the programmer would have had to reprogram the entire app from the ground up again, which would cost too much money. This was a detail I didn't know going in, since I'm not an app programmer. So, I had to live with the app saying that a child scored incorrectly on the final section (substituting final sounds) for several months until the programmer could redo the app over again. I'm happy to say that it's been fixed now, but I had to be patient for that part. My advice (to myself if I write any more apps) is to take the extra time and energy to visualize and think through the entire app -- every single page possible. Visualize the app as it's being used and ask: If I'm doing this in the app, what might I want/need? How will I build the app to allow this to happen? What ELSE might I want/need? Going a little more slowly can pay off a great deal in the end and ensure a very well designed app of which you can be proud. Not that I could have gone much more slowly last time, mind you -- there will probably always be that one thing that you didn't foresee. That's just life, though 2 . Why an App Publisher? You can choose to find someone who knows how to program apps and strike some sort of bargain with them or pay them outright. I