Application frameworks enable developers to rapidly produce new applications –provided that developers are familiar with and experts in using frameworks. Much of what has been written, supported by experience, shows that frameworks are complex, and not easy to learn and use. Unless they have been well understood, and experienced with, the chances of reusability are very limited. The traditional approach of developing an application framework for a particular domain is a separate and independent phase from developing applications. Thus the problem lies in the separation between the process of developing a framework and the on-going process of re-using it to build applications. A newly-introduced framework would be considered complete and is available to developers as a third-party product. It is usually static, complex and for a large segment of developers it is not a re-usable framework. How can developers be convinced to use new frameworks?  This question stands unanswered. In this paper a practical strategy has been presented to help developers building their own frameworks     . This would avoid problems of leaning and using third-party frameworks. Frameworks should evolve from and be reused in the same development environment by the same group of developers. With the support of object-oriented features, application frameworks can be extended in parallel with new software systems being built. This would overcome problems of learning and using third–party frameworks, and would achieve a high degree of systematic reuse.