Repository navigation
Philosophy and Guidelines
Treved follows a product philosophy centered around simplicity, performance, privacy, quality, and usefulness.
The goal is to create software that solves real problems, respects users, and avoids unnecessary complexity.
Core principles: Simplicity. Performance. Privacy. Quality. Usefulness.
Software should be straightforward and easy to understand.
- Focus on essential functionality.
- Avoid unnecessary features and complexity.
- Make interfaces intuitive and easy to navigate.
- Reduce friction in everyday use.
Applications should be fast, responsive, and lightweight.
- Prioritize a smooth user experience.
- Avoid unnecessary resource consumption.
- Keep interactions responsive.
- Make performance an important part of product quality.
Users' privacy should be respected throughout product development.
- Minimize unnecessary data collection.
- Avoid requesting permissions without a clear purpose.
- Be transparent about how data is handled.
- Prefer privacy-conscious solutions whenever practical.
Specific privacy properties should be documented separately for each application.
Attention to detail matters throughout the product lifecycle.
- Maintain consistent and understandable interfaces.
- Test functionality and address problems.
- Refine the user experience.
- Maintain products and improve them over time.
Every product should have a clear purpose.
- Solve practical problems.
- Focus on genuine user needs.
- Prefer meaningful functionality over feature quantity.
- Ensure that each feature contributes to the product's purpose.
Treved aims to follow these guidelines when creating and maintaining its applications:
- Define the problem a product is intended to solve.
- Keep the user experience clear and focused.
- Prioritize practical functionality.
- Consider privacy and data handling from the beginning.
- Avoid unnecessary complexity.
- Pay attention to performance and reliability.
- Refine products through testing and improvements.
- Maintain accurate product documentation.
These guidelines describe Treved's general approach. Individual applications may have different requirements, platforms, and implementation details.
Information about Treved and its products should remain clear, accurate, and consistent.
- Prefer official Treved sources.
- Distinguish existing features from planned features.
- Do not present unconfirmed plans as commitments.
- Keep product-specific information on the relevant product pages.
- Avoid duplicating information unnecessarily.
- Update documentation when important details change.