In 2025, I helped launch Pulse, and today we’re celebrating a major milestone: 1 million visitors. This new homepage is designed to earn that next million by making the fresh categories instantly scannable, with clearer navigation, stronger visual hierarchy, and dedicated space for our fastest‑growing content pillars—so visitors land, recognize what matters to them in seconds, and move deeper into the product experience without friction. https://pulse.us.com
Packaging looks like graphic design. But every word takes physical space.
For Day 19, I built PACKSHIFT an interactive packaging experience where claims, languages, warnings and data become pressure on a finite surface.
It starts with the real 56 mm width of the carton.
Then you try to make everything fit.
Make the box smaller and the pressure becomes physical:
56 mm → pressure → CRACK → recovery → museum
The final package doesn’t just show the solution — it remembers the negotiation that produced it.
Underneath the public game is a deeper spatial compiler built with Blender + Three.js / React Three Fiber, where the same package can open, decompose, expose its dieline, redistribute information and refold.
Packaging is not a file. It is a compiled surface.
Full case study ↓
https://contra.com/p/3WBccUlM-packshift-packaging-is-a-compiled-surface
Live experience ↓
https://packshift-awd.pages.dev/
GitHub ↓
https://github.com/Faadil1/PACKSHIFT
Would love to know which moment lands most for you: Actual Size, the Hydraulic Press, or the Museum?
1
130
The agent saw the truth. Then I changed the world.
Just published THE WORLD CHANGED, an interactive AI agent lab where you change reality after an agent has observed it, then see whether it notices before it acts.
The core interaction is simple:
LOOK → PULL THE GAP → CHANGE THE WORLD → ACT
From there it expands into multiple worlds, a timed challenge, replayable receipts, checked vs. unchecked outcomes, and a genuine recorded Claude Opus 5.5 run.
I wanted the idea to feel physical rather than technical, so the whole visual system is built from passes, tickets, stamps, paper and print misregistration.
Would love feedback on the interaction and art direction.
🔗 https://contra.com/p/FXvqOAEA-the-world-changed-an-interactive-ai-agent-lab
1
114
Contra Community Post
Day 17/30: COMMON ROOM
What if a library card could reveal belonging instead of simply proving access?
I built COMMON ROOM, a speculative membership system for the fictional North Quarter Public Library.
Instead of asking members to choose an identity or complete a personality quiz, the system lets their actual behavior inside the library leave the evidence.
Read in the Stacks → leave a margin.
Make in the Workshop → leave a registration mark.
Follow a question through the Index → leave a reference path.
Explore the Quarter → leave a civic trace.
Those traces gradually build a unique Member Record.
The card remembers in layers. Its physical Accession Aperture later becomes a lens into hidden library memory, and completed cards can optionally become part of a Living Collection that begins to reveal the shape of the neighborhood itself.
The project eventually became a system about:
BEHAVIOR → EVIDENCE → OBJECT → MEMORY → COMMUNITY
And the line that defined the whole thing:
You don’t receive a card. You accumulate one.
I also built the launch film around the same visual logic instead of doing a traditional product walkthrough using the card’s traces, layers and aperture as the motion language.
Would love feedback on one thing in particular:
Does the relationship between behavior, the physical card, and belonging read clearly without needing the concept explained first?
Day 17 of my 30 Days of Real Business Problems challenge.
#ProductDesign #InteractionDesign #CreativeDevelopment #DesignEngineering #MotionDesign #CreativeCoding #ThreeJS #Remotion
3
5
372
DAY 16: CONDITION TRACE
30 Days of Real Business Problems Phase II
I stopped at Day 15.
Not because I ran out of problems.
The format was becoming predictable.
So I changed the rules.
Phase II starts with a problem from museum conservation.
Condition reports can document what was visible at different moments — but they cannot always prove when a physical change actually occurred.
So instead of asking:
“Where did the damage happen?”
I reframed the problem:
Trace when the feature first appears in the documentation.
That became CONDITION TRACE.
The prototype follows a fictional museum-loan case involving the same vessel across four signed condition records.
Earlier examinations were completed under diffuse light.
During the return-arrival inspection, the conservator introduces raking light.
As the grazing angle changes, a hairline crack on the vessel’s upper-right shoulder becomes legible.
That observation is preserved as OBS-04 and carried through a traceable evidence chain:
SRC-03 → OBS-04 → CMP-01 → LIM-01 → FND-01
But the system deliberately refuses to overstate what the evidence proves.
The earlier examinations were not performed under equivalent lighting conditions.
So the conclusion remains narrow:
FIRST DOCUMENTED APPEARANCE AUGUST 3, 2026
Not:
“The damage happened on August 3.”
Not cause.
Not responsibility.
Not liability.
The interface follows the same principle.
Light becomes an examination instrument.
The observation persists through comparison.
The evidence lineage remains visible.
And the final finding must be deliberately sealed.
The goal wasn’t to make an interface that looks forensic.
It was to make the boundary of the evidence visible and traceable.
TRACE THE RECORD. NOT THE BLAME.
Live prototype:
https://day16-condition-trace.vercel.app
Day 16 / 30
Phase II begins.
AI Product Designer & Design Engineer for SaaS & AI Startups
AI Product Designer & Design Engineer for SaaS & AI Startups
I have created the design for altystick.be, but also the plugin that lets the user create their own sticker.
1
77
I contributed to the Product Design and Development of LinguaMD, helping shape the user experience and interface design of this innovative healthcare communication platform. I worked on creating intuitive workflows that streamline doctor-patient interactions while ensuring the platform remains secure and compliant with healthcare data protection standards.
1
83
I contributed to the Product Design and Development of Featcal, helping create an intuitive platform that streamlines nutrition follow-up workflows. I worked on designing the user experience for both healthcare professionals and their patients, ensuring the platform is secure, compliant with healthcare standards, and easy to use for clients of all technical skill levels.