Pintu Kumar raj

It s funny how all our automated tests can pass with 100% green checks and yet a simple user action like hitting the browser's Back arrow completely breaks the app experience.

I spent hours debugging why an onboarding wizard kept dragging finished users backward because of how router pushes stack up in Next.js. Unit tests just don't catch browser level history states unless you're running heavy end-to-end browser tests.

For UI flows with multiple steps do you rely on tools like Playwright to test history behavior or is this just one of those things you catch manually by testing it yourself?

It s so easy to fall into the trap of forcing the exact same card or button component onto every single screen just to keep the design system clean.

I ve worked on projects where sticking blindly to the rulebook made a simple workflow feel super awkward for the user just because we didn't want to break the pattern. A tidy layout looks nice on a Figma board, but if it makes the actual task harder it defeats the purpose.

How do you guys decide when it's okay to break the system rules for a better user flow?

I used to set up a meeting for literally every small update just because it felt easier than typing out a long explanation.

Then I realized half those calls ended up with everyone just staring at each other while I explained something that could have easily been a quick bullet point list in Slack. Now I try to ask myself if a quick text update can do the job before sending out a calendar invite.

How do you usually filter out unnecessary meetings from your schedule?