Prototype
One of the goals of object-oriented programming is to close the time gap between application design and application testing. The sooner you can get a prototype of an application, the better. The longer an application's "gestation" period, the greater the risk that the application will be unacceptable. If you deliver an application that took a long time to create, you will often find that the original application specifications are wrong, the needs of the customer have changed, and/or that your customer's management has changed (placing you in an uncomfortable political situation). While none of these is your fault, you will suffer the consequences nonetheless.
Object-oriented programming techniques are ideally suited for creating and delivering applications as a series of revisions or prototypes. You can use the Studio to create and test entry views almost immediately. Feedback you receive here will allow you to ensure that your view’s appearance and navigation behaviors are proper. If you follow the "leave well-enough alone" philosophy, you will be able to create working views, assemble your application, and deliver your "first-pass" version. Then, based on (enthusiastic) user feedback and lists of desired enhancements, you can deliver your more polished application.
This development philosophy ensures that you continually progress in the right direction and helps you to avoid getting bogged down making minor (and often inconsequential) changes.