About

I build software around real problems

I’m Gabriel Sgroi, an independent developer working across medical management, data, and software development.

I build focused macOS tools that make everyday tasks clearer and more efficient. My work usually starts with a simple observation: something takes too many steps, information is difficult to access, or an existing process could work better.

I enjoy turning these observations into practical software—tools that are easy to understand, reliable in daily use, and focused on doing one thing well.

Where I come from

I studied International Management for Business and Information Technology at DHBW Stuttgart. I live in the Stuttgart region, an area strongly shaped by engineering, manufacturing, and innovation.

The region is closely connected to the development of the automobile, the Zeppelin airship, and many other innovations that have shaped modern industry. But what interests me most is not the history itself. It is the mindset behind it: precision, practical thinking, disciplined work, and the willingness to turn an idea into something real.

That environment has influenced how I approach my own work. I value clear thinking, reliable systems, and solutions that are useful beyond the initial idea. Often, progress does not begin with a completely new invention. It begins with improving an existing process or making something work more smoothly.

What I do

For nearly five years, I have worked in medical management for a regional hospital association.

My work combines process improvement, data management, and practical problem-solving. I work with information that needs to be structured, maintained, and made useful to the people working with it.

Healthcare is a complex environment. It involves many different people, large amounts of data, and processes where accuracy and reliability matter. Even small improvements can make a noticeable difference when they remove unnecessary steps or make important information easier to manage.

This work has taught me to look beyond individual tasks and understand the systems behind them. Before trying to improve something, I want to understand how it works, where the dependencies are, and what effect a change will have on the people using it.

That perspective influences everything I build as a developer.

What I build

Outside of my professional work, I develop my own software for macOS.

I am interested in tools that quietly improve the way people work. They do not need to be large or overloaded with features. They need to solve a specific problem well and fit naturally into the user’s existing workflow.

This approach is reflected in the tools I am currently building: focused menu bar applications that make common actions faster and easier. Whether it is opening a frequently used folder or accessing a two-factor authentication code, the goal is the same—to reduce unnecessary friction without adding another complicated system.

I enjoy the complete process of development. It starts with identifying a problem, then continues through research, design, implementation, testing, and refinement. Each stage reveals something new about the original idea.

The best result is when a tool becomes so clear that it no longer needs explanation. It simply works.

How I think about software

Minimalism is an important part of my product philosophy.

Adding another feature is usually easy. Deciding what does not belong is much more difficult. A product can offer many possibilities and still fail to provide a clear experience. The challenge is to find the right balance between capability and simplicity.

For me, good software does not try to do everything. It focuses on the essential problem and handles it carefully.

That includes the details: the wording of a button, the number of steps in a workflow, the way information is organized, and what happens when something does not go as expected. These decisions may seem minor individually, but together they determine whether a product feels effortless or unnecessarily complicated.

Minimalism is not about making software empty or limited. It is about removing what is unnecessary so that the useful parts become easier to see and use.

My technical foundation

My primary technical focus is database architecture and the systems built around reliable data.

I enjoy designing structures that are clear, consistent, and capable of supporting a product over time. Good data architecture creates a solid foundation for everything built on top of it—from internal processes to user-facing applications.

Working with databases has also shaped the way I think about software more generally. I pay attention to relationships, dependencies, consistency, and long-term maintainability. A system should not only work today; it should remain understandable and adaptable as requirements change.

Whether I am improving a process in medical management or building a small application independently, I care about the same principles: a clear structure, a reliable foundation, and a result that solves a real problem.