Back to work
Frontend experiment
Slot Machine Game Experiment
A browser game prototype used to explore state, feedback, probability and playful interface motion.
Challenge
- Game UI needs immediate feedback, clear state changes and enough polish to feel intentional.
- Probability and payout rules should be understandable in code without making the interface feel mechanical.
- Animation has to support the interaction instead of hiding unclear logic.
Solution
- Structured the prototype around explicit spin states, result states and payout feedback.
- Used a compact visual system that makes the reels, result and call-to-action easy to scan.
- Treated the experiment as a way to sharpen product-level interaction judgment, not just make something playful.
Outcome
- The prototype becomes a small test bed for animation timing, state machines and UI feedback.
- The same thinking transfers into dashboards, tools and forms where status changes need to feel clear.
- The project adds a more experimental edge to the portfolio without distracting from practical client work.
Stack and patterns
Built as a state and interaction experiment with reusable frontend lessons.
ReactCanvas conceptsState machine thinkingAnimation timingProbability rulesInteraction feedback
Your product needs feedback that feels immediate.
Dashboards, tools and games all benefit when state changes, rewards and errors are obvious without extra explanation.
Prototype the most important state loop.
Start with one action, one response, one success state and one failure state before polishing the rest.
The interaction that feels flat today.
The fastest improvement comes from a concrete moment where users need clearer feedback or confidence.
Previous proofAI Response Evaluation HackathonAI evaluation hackathon / 2026
A quality workflow that makes AI output easier to judge, compare and improve.
Next proofEnterprise Automation ConceptsEnterprise workflow concepts / 2026An operations layer that removes manual handoffs by making systems talk to each other.
My process
A clear path from idea to impact.
Clarify
We define the problem, users and constraints before anything gets overbuilt.
Prototype
I design the core workflow quickly so direction becomes visible early.
Build
I build clean, scalable foundations with attention to detail.
Ship
We launch, test with real users and make sure it actually works.
Improve
I iterate, optimize and evolve the product with your team.
Practical. Collaborative. Built to last.
Let's work together
Tell me what you want to build.
Let's build something useful.Project brief
Shape the first message.
Choose the build, name the friction, then send Pontus a brief that already has structure.Hi Pontus, I am interested in: A conversion-focused website. Main friction: The current experience does not create enough confidence. Timeline: Soon. Context: What makes the current site, tool or workflow feel less trustworthy than it should? Useful starting point: Pontus should review the current offer, page structure, audience and strongest proof points. Best,
What Pontus will ask next
- Who needs to trust you faster?
- What should visitors do next?
- What proof already exists?
A conversion-focused websiteSoon