Table 5 How the different platform boundary resources supported or hindered the use and adoption of Qt

Application boundary resources:

API capabilities

Supports adoption: used to justify selecting a framework

Unfamiliarity of the programming languages

Hinders adoption: adds to the learning curve

Specialized APIs for different developers and purposes

Supports use: improves productivity

Hinders use: if lacks necessary features

Framework source code available

Supports use: improves framework visibility

Supports adoption: ensures framework continuity

Development boundary resources:

Difficulty in installing tools or initializing projects

Hinders adoption: getting started takes time and effort

Unnecessary libraries in installed tools

Hinders adoption: download size, unexpected issues

Complicated deployment

Hinders (initial) use: major showstopper

Editor capabilities and embedded documentation

Supports use: improves efficiency

Social boundary resources:

Personal recommendation and peer experiences

Supports adoption: are valued when selecting the framework

Active, long-lived community

Supports adoption: continuity is important when selecting the framework

Insufficient or irrelevant information on getting started

Hinders adoption: not adequate guidance

Information not targeted and organized for developers’

Hinders use: lowers satisfaction, searching

needs

information takes too much time

Code examples, videos

Supports use: give easy-to-apply, hands-on guidance

Peer help, online or face-to-face

Supports use: sharing knowledge about similar problems