Behind the products
How we build
Different products need different tools. We choose technology around the work it needs to do and our ability to maintain it.
Product rules
We begin with the rules, inputs, and exceptions a product needs to handle. Where a result depends on assumptions, those should be clear to the person using it.
Interfaces
People should be able to see what a product does, what it needs from them, and what happens next. We use that as the starting point for the interface.
Shared services
The Stretx account service gives products a shared foundation for identity and account management. The website introduces the products; account management lives in its own application.
Ongoing development
Maintenance, testing, and documentation are part of running our software. We consider those needs when choosing libraries and planning changes.