Tymly has been designed by West Midlands Fire Service to help meet the challenges facing today’s public sector. We combine open source software and open standards to offer a fresh alternative for teams delivering digital services.
In Tymly, all digital services emanate from a single source... this means users only need use a single app! This approach not only offers a great user experience, but it also greatly reduces IT headaches such as training and user-management.
Tymly allows users to access all their digital services from any device, anywhere. We've worked closely with a variety of industry experts to ensure the Tymly app works securely, quickly and reliably... be it in the office or out in the field.
Another advantage of the Tymly approach is that users have immediate access to any piece of information from any digital service they're part of. We've used a search specialist to help ensure Tymly returns the most relevant results in the quickest time.
Within Tymly, "blueprints" allow organisations to document their digital services via a set of open standards. They're a great asset that can help interoperability, share best practice and avoid traditional vendor lock-in woe.
Tymly takes a batteries-included approach and ships with a library of components to model most business processes. Under the bonnet, a plugin architecture allows organisations to introduce specialist components - if the need ever arises.
As per Government Digital Service recommendations, we build Tymly "in the open" on Github. We use modern software tools and practices and love contributions from other teams. Tymly can be controlled via a secure REST API too!
Yes. The Tymly monorepo is maintained by West Midlands Fire Service and is downloadable via Github under the MIT License. Read more about our open source ethos here.
Yes. in Tymly, blueprints provide a way to describe some related components that can coalesce to produce a digital service. Please see our technical documentation to get stuck in!
Tymly uses Finite State Machines to undertake any task, large or small. These state machines can be created, updated and cancelled via a secure REST API - this allows external systems to integrate with the digital services offered via Tymly using simple and well proven web protocols. Conversely, state machines can invoke external REST APIs to request and manipulate data via third party services too.
In Tymly, data models are defined inside blueprints using the open JSON Schema format. This allows for a No-SQL-style experience when interacting with data. However, under the bonnet, Tymly will transparently use these schema definitions to conjure more traditional relational tables in PostgreSQL. This in-turn brings benefits in terms of querying, data integrity and tooling. The best of both worlds!
Yes please! Be sure to first read our Code of Conduct and Contributing docs though... and then either raise an issue, or better still throw a pull request our way! Note we use the Standard.js code style - the tests won't pass if things fail linting.
