The Experience
From cat photos
to custom calendars.
Browse and filter cat pictures, upload your own images, save favorites, and build personalized calendars. Both the Next.js and SvelteKit versions are functionally complete, including calendar creation.
-
Browse & filter
Explore cat photos by breed, category, and more.
-
Bring your own
Upload personal pictures for a calendar that feels like yours.
-
Save favorites
Build a collection of photos to come back to.
-
Create calendars
Turn the pictures you choose into personalized calendars.
A collection of your own
Keep favorite cat photos and your uploads close at hand for calendar creation.
A playful starting point
The home screen introduces the app and offers two ways to begin: browse or upload.
Three Implementations
Same app.
Different frameworks.
Keeping the feature requirements consistent gives me a practical way to compare developer experience, architecture, and reactivity. Next.js and SvelteKit are complete; the Nuxt version is still in progress.
-
Next.js / React
CompleteA complete implementation, including calendar creation, with a live demo to explore.
Exploring React composition, state, and Next.js routing against the same application requirements.
Try the Live App -
SvelteKit / Svelte
CompleteThe same full feature set, including calendar creation, implemented in SvelteKit.
Comparing Svelte’s reactivity and component model with the React implementation.
-
Nuxt / Vue
In progressA third implementation underway, bringing the same application requirements to Vue.
Exploring Vue’s composition patterns and Nuxt’s application conventions as I build.
Shared Foundations
Consistent core.
Framework flexibility.
A common set of persistence and styling tools helps keep the comparison focused on framework choices. These are the shared foundations for the complete versions and the Nuxt implementation as it develops.
-
Dexie / IndexedDB
Browser-side local persistence for application data, favorites, and uploaded images.
-
Tailwind CSS
Shared utility styling keeps the visual language consistent across frameworks.
-
DaisyUI
Shared UI patterns and components support a familiar experience in each implementation.
What I’m Exploring
A hands-on comparison.
Building the same features in different ecosystems turns abstract differences into practical questions. These are the areas I’m exploring as the project evolves.
-
Component composition
How does each framework organize reusable UI and connect components?
-
State & reactivity
How do changes to filters, favorites, and calendar choices flow through the interface?
-
Routing & architecture
How do routing conventions and project structure shape the application?
-
Developer experience
What is it like to build, debug, and iterate on the same features in each ecosystem?
-
Performance
How might loading, rendering, and runtime behavior differ? An area to investigate, rather than a benchmark claim.
-
Practical tradeoffs
Which approaches feel natural for a feature, and where do they introduce complexity?
The Bigger Picture
Curiosity that
builds skills.
I stay hands-on by building things that make me curious. Cat Calendar Creator gives me room to experiment across ecosystems, work through real application decisions, and keep learning through the process of making something complete.
Same cats. Different frameworks.
A lot to learn—and a lot of fun.

