DK · Senior Software Engineer
Complex product features
Professional work
Customer-facing product work where the interface, the rules, and the state all have to be right together.
Contributing engineer. These were team efforts. 2021 – Present. Shipped as part of the wider product. No private screenshots.
Overview
Some of the harder UI work has been product behaviour rather than a marketing page. That includes responsible gaming interfaces, jackpot experiences, account functionality, and location-aware experiences. I contributed as part of the team. I did not own the products alone.
The problem
These features are full of rules. What the person is allowed to see, what must be confirmed, what changes with where they are, and what has to stay consistent if they refresh or come back tomorrow. A component that only matches a still image is not finished.
Architecture
The useful structure is a small set of reusable pieces with state that matches the rules, sitting on the same Remix and React frontend as the rest of the site. Location and account behaviour depend on services I will not describe here. The frontend job is to make those responses legible and hard to misuse.
Decisions
- Model the rules in one place so a jackpot or a safer-gambling limit does not get reimplemented in every view.
- Design the empty, loading, and refused states with the same care as the success state.
- Keep copy and interaction accessible. These screens are used by people, not only by a demo.
Trade-offs
- A generic component saves time until a product rule does not fit it. Forcing the rule into the generic component is worse than a specific one. I would rather have a smaller abstraction that tells the truth.
Where it stands
The work shipped with the products. I am not attaching conversion, revenue, or engagement numbers. I also will not publish screens of account or safer-gambling flows.
High-level only. No private product designs.
Stack
- React
- Remix
- TypeScript
- Accessibility
- State management
Back to lekker.dev