This blog records wisdom gathered through projects. After wrestling with other ideas, Perretex arrived: a place where anyone could have a dog linked to "their" user, be the owner, and like or comment on others' dogs. It sounds simple; in practice, it forces you to think about identity, persistence, and permissions.

No Database, No Lasting Changes

At first, you can mock screens and simulate data in memory. But as soon as you want likes and comments to stay there tomorrow, and someone else to see what happened, the browser alone isn't enough: you need a place to store rows in an orderly way. That's when I realized: I needed a database (or, essentially, a backend with storage; same idea: something reliable that doesn't vanish when the tab closes).

It was a classic lesson: the product pushes the data model. First, you think "dog profile"; then "who owns this dog?"; then "who can comment here?". Without linked tables or documents, it gets messy fast.

What I Discovered: Traditional Registration Isn't Always Necessary

I had the usual script in mind: registration form, email, password, verification... While reading docs and examples, I found a different approach: a new user can be created automatically upon entering the site, without manual sign-up. In practice, this is usually linked to a session, cookie, or identifier that the site recognizes on return visits.

This changes the experience: the visitor doesn't fill out a "create account" form to start; they can already create their dog, appear as the owner, and interact (likes, comments) with the data ecosystem behind the scenes.

It's not magic: it's still identity persisted on the server, just a quieter flow than the one I had in my mental script.

Core Takeaways

• Persistence first: If you want owners, likes, and comments between different people, you need a common place for the data.
• Research before implementing the heavy flow: Sometimes there are patterns that reduce friction (anonymous or automatic users) that fit exactly what you're looking for.
• Be honest about limits: If the link is browser or device-based, you must know what happens if someone clears local data or changes phones — it's a design choice, not an afterthought.

Perretex taught me that even a minimal social network (even for dogs) is already a data problem. And leveraging what tools already offer can save you from forcing every visitor through a sign-up they might not even need.