About

Made for my own everyday life. Shared for yours.

Why Pearrolls began

Pearrolls began with tools I needed and wanted to use myself. As I used them, I thought they could help someone else too. That is why I started sharing them.

pearrolls

Software for everyday life

The need behind the first product

HaruSync

Using separate apps for schedules, tasks, notes, and a diary felt cumbersome. I wanted to manage them in one place, and to organize schedules and tasks around goals I wanted to achieve. That need became HaruSync, Pearrolls’s first product.

Explore the product

How I refine it

When something feels inconvenient, I want to understand why and build a better way. The aim is to make that improvement useful to more people who face the same friction.

I care about the details and do not rush something out just because it runs. I use it myself, check how it behaves, and refine the experience before sharing it. After release, that work continues with everyday use and feedback.

Small details. Lasting care.

Start with a real need

A clearer plan. Hearing how you speak. We start with the moments when a tool is needed.

Keep the experience clear

Give every feature a purpose, and make the next action easy to find.

Keep making it better

Listen, use, refine. A launch is the beginning of caring for a product.

Explore our products

The craft behind the products

I work across apps, desktop software, servers, and infrastructure, choosing technologies to suit the problem. These are the languages and tools I use.

Main languages
  • C++
  • Python
  • Dart
  • Go
  • JavaScript
  • TypeScript
Frameworks & platforms
  • MFC
  • Flutter
  • Node.js
  • React
Data & infrastructure
  • Linux
  • GCP
  • Docker
  • Kubernetes
  • RDBMS
  • NoSQL