What is Kipple?

@bdrelling is always working on far too many projects across far too many codebases at any given time.

Every software project may be unique in it sown way, but we also know that they share many of the same building blocks with one another: a networking layer, diagnostics middleware, CI/CD workflows, and so on. A majority of these building blocks can be nearly identical, especially in the short- to mid-term life of a project, but a one-size-fits-all solution just doesn't work for scalability, and the wrong short-term decision can end up putting heaps of technical debt on an organization.

Kipple aims to provide a collection of these common modules, ready to reference for inspiration or drop into projects and start using, all without pretending to be a "long-term" framework that bloats your application or causes technical debt in the future.

Goals

• 📦 Create a collection of common modules typical to any given application's lifecycle.
• 📖 Document and demonstrate usage of these modules as thoroughly as possible, as well as overall concepts of application modularization.
• 📋 Provide easy access to code snippets and concepts that can be cut and pasted directly out of the repository with limited issue, without pulling in as a dependency directly.
• 📱 Open-source production applications, so others can see how these modules are integrated and used in real-world scenarios.

Support

Your support will help me find time to write articles, provide better examples, improve documentation and testing for all modules, and eventually open-source applications that are live in the App Store for use in education and inspiration.

Every little bit helps, and it is extremely appreciated!