Simplicity, done well.
Beautiful to look at. Natural to use.
Software and hardware that work without a manual.
From mobile apps to medical devices, every decision starts from the experience of those who use them every day.
The principles behind every project
Every product developed is grounded in a set of values that guide architectural and design decisions.
People First
Each project begins with the observation of real people: their mental models, expectations and behaviors. The interface adapts to the user, following the school of Don Norman.
Security & Privacy by Design
Security and privacy are architectural choices from the very first line of code, not afterthoughts. Data stays under the user's control, stored in the EU in compliance with GDPR.
Poka Yoke
Every system is designed to make errors difficult before they occur. Asymmetric connectors, guided flows, interfaces that leave no room for ambiguity: prevention is worth more than correction.
Open Source
Preference for open, interoperable standards. No dependency on proprietary protocols: systems must be able to communicate with the existing ecosystem.
Simplicity
Complexity is absorbed by the product, not transferred to the user. Every interface, every flow, every design decision aims to reduce cognitive load.
Form
Aesthetic quality and functional quality are indistinguishable. Form is not a finishing touch: it is a project requirement from day one, in both code and hardware.
The method
Decisions do not happen by chance. Principles consolidated over time guide every choice, from the first prototype to the product in production.
Problem first, technology second
Every project starts with the observation of people and the context in which they operate. Technology follows the understanding of the problem, never the other way around.
Products above all
The core of the work is proprietary products, built around real problems observed directly in the field. Solutions born from within, not answers to briefs.
Full stack, single vision
A single vision spans hardware, firmware, cloud and UX. The product grows as a coherent system, with no fractures between technical layers.
Iteration over time, not isolated sprints
Yoovant's products have long life cycles. Value is built through real-world use, not exhausted at launch.
Beauty is not optional
Even where no one is watching
Thirty years of projects have confirmed that products which stand the test of time are those where aesthetic and functional quality are indistinguishable. Without a final "beautification" phase. Simply because form was already in mind from day one, alongside function.
A kind of dialogue emerges between the board and its enclosure, and that dialogue leads to unexpected discoveries, forms that no one had sought. A flower along the PCB traces, or a silhouette that shifts and finds its own new meaning. From that moment, the form becomes a technical requirement that has no audience. It will remain hidden inside the device forever.
It is the most sincere form of care.
From idea to market-ready solution
Medical devices, IoT systems, mobile apps, management software.
Different sectors, same approach.
Omiari - HealthTech
Medical device addressing the problem of low pharmacological therapy adherence, with voice commands, cloud software and a mobile app. Italian patent for industrial invention already obtained and positive PCT outcome. In development
Yooquik - Wireless home automation
Open Source IoT platform for continuous monitoring. Low-power MEMS sensors, evolving toward LoRa and AI. Yooquik's technologies find their natural evolution in the Omiari ecosystem. In evolution
Easeeapp - Data collection for retail
iPad application for in-store data collection in large-scale retail. Structured data gathering, validation rules, area management and multi-level supervision. Visit route planning.
Simple - Management software
Business management software for SMEs, craftsmen and professionals: inventory, sales, accounting, due dates. Three modular versions to fit businesses of different sizes. Legacy project
Building a product requires decisions you make only once
Architecture, stack, the balance between hardware and software: every choice made in the first weeks shapes everything that follows. Even when building an MVP. Someone who has already been through that journey with their own products is trained to ask different questions, well before problems arise.
Architecture and technology choices
Evaluating options against real constraints: budget, team composition, security requirements, scalability over time. Architectural decisions are paid for, or rewarded, for years.
Hardware, firmware and software
When the product requires physical components, sensors, actuators, wireless communication, a unified vision across the full stack reduces blind spots and misunderstandings between layers.
UX and user behavior
Interfaces that require no manual are not designed by intuition. They are built by observing how real people use things: the mental models they bring with them, the implicit expectations and the errors they tend to make.
From prototype to market
Validation, certifications, iteration, distribution: each phase brings its own specific pitfalls. Recognizing them early changes the kind of questions asked, and the cost of the answers.
Let's talk
For collaborations, technical consulting or simply to explore ideas together.
Email
LinkedIn
GitHub