ROLE
Speculative UX Designer
RESPONSIBILITIES
Concept development & worldbuilding
AI-generated art & visual design
UX/UI & interaction design
No-code development & motion integration
This project started as a challenge: What could I build if I completely stepped outside traditional expectations of web design? Without a development background, I wanted to push the limits of no-code tools, AI-generated visuals, and interactive storytelling to create something unexpected, immersive, and entirely my own. The result is Galaxy X832p-19, a speculative exoplantetary experience that transforms a simple webpage into a seamless, motion-rich world—built entirely in Framer.
This wasn’t about following best practices or replicating existing trends. It was about breaking out of conventional UX/UI structures and seeing how far I could take an experience using only the tools available to me.
CHALLENGE
The ultimate goal was to experiment, explore, and prove what was possible without relying on traditional development. Could I, alone, create a truly immersive digital experience without a single line of code? Could I make AI-generated imagery feel cohesive and intentional, rather than generic? And most importantly—could I design an experience that felt completely unlike a standard portfolio case study or website?
Traditional UX/UI projects focus on solving problems. This one was about pushing creative boundaries for the sake of discovery.
ONE
PROCESS
This portfolio website was the first thing I ever built in Framer, and I approached it in a fairly traditional way—creating a clean, structured layout that showcased my work. At the time, I was focused on understanding how the platform functioned, learning the basics of building pages, structuring content, incorporating interaction, and ensuring responsiveness. But as I worked with Framer more, I started to see its potential beyond traditional web layouts. The platform wasn’t just a tool for polished, static pages; it could be a playground for something much more experimental and interactive.
That realization led to this project. I wanted to push myself to see how much I could accomplish within Framer, exploring how motion, layering, and effects could create an experience that felt unexpected and immersive. I started by learning how scroll animations worked, how absolute and relative positioning affected interactions, and how the Z-index controlled depth and layering. I experimented with Framer’s style and effects toolkit, testing different ways to create seamless, intuitive motion that felt engaging rather than purely decorative.
Rather than following a fixed plan, I let the project evolve through experimentation. Every time I learned something new—whether it was a way to create parallax depth or a technique for making smooth transitions—it inspired the next step in the design. Each discovery unlocked new possibilities, turning what started as an idea into a fully realized, immersive world.
TWO
EXECUTION
Once I had a grasp of the core mechanics, the real challenge began. Executing the vision was anything but straightforward. Each animation, transition, and interaction required constant iteration. What worked in theory often fell apart in practice, forcing me into a cycle of trial, error, and refinement.
One of the biggest challenges was ensuring smooth, natural motion across the entire experience. Scroll-based animations had to feel fluid rather than rigid, and every interaction needed to be seamless and intuitive. That meant constantly tweaking easing curves, layering elements correctly, and finding ways to work around the limitations of no-code tools.
Creating depth and layering effects that felt immersive required precision. Adjusting the Z-index, fine-tuning positioning, and making sure elements moved in ways that made sense within the larger visual system took countless iterations. Some interactions that seemed simple at first proved unexpectedly complex to implement, leading to a process of constant problem-solving—try something, see it didn’t work, try something else, and repeat.
There was no predefined roadmap, no tutorial to follow step by step. Every part of the execution required thinking through interactions in a way that made sense for the experience and then testing, adjusting, and refining until it felt right. The entire process was an exercise in persistence, experimentation, and pushing past technical limitations to create something that felt truly immersive.
THREE
WHAT I LEARNED
Galaxy X832P-19 was more than just an experiment—it was proof that creativity isn’t limited by technical expertise. In fact, it could be argued that technical expertise is sometimes a barrier to creativity. The biggest lesson? You don’t need to be a developer to build something that feels cutting-edge.
Beyond that, this project helped me more fully grasp the structure and functionality of how the internet works. My previously basic understanding of CSS and HTML finally clicked in a practical way. Concepts like positioning, layering, and responsiveness that had once felt abstract became tangible as I worked through the challenges of building an interactive experience. I now have a much clearer sense of what developers do and how design decisions translate into code, which will make me a stronger collaborator in future projects.
I discovered how AI can be a tool for concept development, not just automation, shaping an artistic vision rather than replacing it. I learned how motion design and interaction can transform static UX into something cinematic. And most importantly, I proved to myself that the best work often comes from setting your own challenges, rather than waiting for a problem to solve.
FOUR
OUTCOME & NEXT STEPS
This project redefined how I approach digital design. The ability to create immersive, motion-driven, AI-enhanced storytelling without writing a single line of code opened up entirely new possibilities for my work. Moving forward, I plan to explore dynamic AI-generated content, interactive 3D elements, and even more unconventional web experiences that push design beyond traditional expectations.
While I did try to make this adaptive across devices, experiencing it on desktop far outshines the mobile experience. Given the scope and detail of the worlds portrayed, I ultimately decided that optimizing for mobile would require repositioning hundreds of elements, which would compromise the integrity of the design. Instead of forcing a mobile adaptation, I embraced this as a desktop-specific experience. That said, it would be interesting to design something similar with a mobile-first or mobile-only approach, exploring how interactivity and motion could be reimagined for a smaller screen with different interaction patterns while still maintaining a sense of immersion.
For now, Galaxy X832P-19 stands as a testament to the idea that the best way to grow as a designer is to throw out the rulebook and just see what happens.
