Speed of development

The number one priority of Sapling is speed of development.

Sapling was born out of frustration with incumbent frameworks requiring huge amounts of setup and boilerplate code to do even the simplest things. Even if there are good reasons for these frameworks to work that way, spending huge amounts of time doing things The Right Way isn't always the sensible thing to focus on in every project.

Importantly, Sapling doesn't have to be the best framework for every purpose. You would be very right to pick something else for your team of 150 devs to work on your monolithic military grade banking platform.

By focusing on minimising the setup and boilerplate errands, Sapling instead shines for projects where just getting it out there is the most sensible priority:

• MVPs
• Prototypes
• Proofs of concept
• Hackathons
• Challenges
• Side projects
• Weekend hacks
• Test environments