From Idea to Public Launch

I owned all of it: research, design, code, launch, growth.

I did research and realized sprint reviews were just the tip of the iceberg. When I deep-dived into team workflows, I uncovered additional friction points:

That became my design challenge. How could I bridge the mobile-desktop divide instead of letting old habits dictate our workflows?

I brought the problem directly to the Product Owner and IT leadership, laid out the case for fixing it, and got the green light to build a solution.

I started by going back through recordings of old sprint reviews and meetings to see how the team actually worked. Then I talked to people across the team. The pattern was clear: any solution that added steps would just create new friction on top of the old one.

I designed the initial concepts in Figma and worked closely with a developer, testing and iterating. Our rule: one click, both views immediately. No configuration, no learning curve. Because the moment someone has to stop and think about the tool, it's already failed.

Almost every feature started with early internal tests. I invited team members to try out early builds and quickly noticed a major hardware split: people were working on completely different setups, some on massive monitors, others on small laptop screens.

This made screen-sharing during sprint reviews messy. I had to adjust how the extension scaled so that no matter what screen size someone shared, the side-by-side view stayed crisp and easy for everyone to read.

Both IT and Marketing adopted it without any mandate. It just became the default: no onboarding, no push, no training.

The best part: it marketed itself. People saw it on someone else's screen during a call and immediately asked how they could get it too.

After seeing how well it worked internally, I decided to take the core idea public. I built the public version from scratch, completely separate from Polska Press infrastructure and codebase. They knew about it and cheered it on.

It was also a deliberate experiment: could I build a real product alone and keep it from looking generic? I redesigned the UI to match Chrome's aesthetic and checked every output. Beating AI slop became its own design discipline.

Through 20+ qualitative interviews with product teams, sales reps, and agency workers, I dug into how they managed past presentations and where workflows broke down.

These sessions revealed that a simple side-by-side view solved 90% of needs, so I designed an ultra-minimal UI keeping advanced tools one layer deeper:

The best part wasn't the numbers. It was realizing how fast I can ship and watching others rely on it every day.

Warm praise across the design community with flawless 5/5 reviews. Organic traction driven entirely by word-of-mouth: zero emails, ads, or push notifications.