Table 7 Recommendations for the framework owner to support the developer journey
From: Development as a journey: factors supporting the adoption and use of software frameworks
1 | Consider the whole developer experience, including usability and enjoyment, and all platform boundary resources. |
2 | Consider the whole developer journey and support developers in different journey phases. |
3 | Pay specific attention to framework adoption and initial use; that is, to ease of getting started, installing tools, initializing projects and deploying applications. |
4 | Design API capabilities and select the programming languages to match developers’ know-how and application development purposes. |
5 | Focus on information quality, not quantity: centralize information sources, avoid redundancy, and communicate information sources and their target audience, for example, in a boundary resource map. |
6 | Provide both high-level documentation and low-level, e.g., method-level documentation; the high-level documentation should explain the framework’s big picture. |
7 | Participate in building and sustaining an active community around the framework; this ensures peer help, peer recommendation and visibility of the framework. |
8 | Evolve the framework actively and convince developers about the framework’s continuity; publishing the framework as open source is one way to do this. |