Like many of you, I have thousands of photos spread across devices, cloud drives, and chat histories. Finding that one specific picture from "last summer's beach trip" meant endless scrolling. Folders and filenames don't help when you can't remember when or where you saved something.Morse Code Translator
So I built a tool to fix my own problem. It turned into a real product.
What It Does
Upload your photos, and the AI analyzes each one — it sees what's in the image, describes it, tags objects, identifies scenes, even reads text embedded in the picture. Then you search in plain language: "my dog on the sofa" or "sunset at the beach" or "the menu from that restaurant in Shanghai."
It works in both Chinese and English, with the entire interface adapting to your language preference.
The Core Problem: Search Is the Killer Feature
Cloud storage is a solved problem. What's not solved is finding things later.
Traditional photo apps rely on you to organize — create albums, add tags, remember dates. That's work. Nobody does it consistently. AI flips this: you don't organize anything. You just describe what you want, and the system finds it.
The search combines two approaches. One looks for literal keyword matches across filenames and tags. The other uses semantic understanding — it knows that "evening glow" and "sunset" are related, or that a photo of a "labrador retriever playing fetch" matches "dog at the park."
The magic is in merging these two results intelligently so the most relevant photos surface first. Users don't need to know any of this — they just type and get results.
Why AI Vision, Not Just Metadata
A lot of photo tools auto-tag based on EXIF data or basic object detection. That's useful but shallow. A vision-language model can tell you:
- The mood of a photo (cozy, energetic, melancholic)
- The context (wedding reception, not just "people standing")
- The text in a sign, menu, or document
- The color palette (useful for designers and creators)
This turns search from "find files named beach_2023.jpg" into "find that photo where I'm wearing a blue shirt and holding a coffee cup."
The Business Model
The app offers a generous free tier so anyone can try the AI features without friction. When users hit the limits and see real value, they upgrade to a paid plan with higher quotas.
This is important: the free tier isn't a gimmick. Users need to experience AI understanding their own photos before they'll pay for it. A demo video doesn't convince anyone — but seeing the AI correctly describe your own vacation photos? That converts.
Lessons From Building a Real Product (Not Just a Side Project)
1. AI Costs Are Real — Design Around Them
Every image analysis costs money. You can't just throw every upload at the model without thinking. Compression before upload, smart caching of results, and per-user quota tracking are not "nice to haves" — they're the difference between a viable business and burning money.
2. Bilingual Support From Day One Matters
I built this with Chinese and English support baked in, not bolted on later. The AI even responds in the user's language. Retrofitting i18n is painful; doing it from the start is surprisingly manageable with tools like next-intl.
3. The Free Tier Is Your Marketing Engine
Word of mouth works when people can show the product to friends without pulling out a credit card. Multiple paid users told me they upgraded because they hit the free limit while showing off the AI features to colleagues.
4. Type Safety vs. Build Environment: A Real-World Debugging Story
The toughest technical challenge wasn't the AI integration or the vector search — it was a TypeScript type inference bug that only appeared on Vercel's build environment, not locally. Same code, same TypeScript version, completely different behavior.
The issue was in how the Supabase client library's generic types resolved on Vercel's bundled TypeScript. Every database call chain produced never types at build time. It took three iterations to find a consistent workaround. This kind of environment-specific build issue is something no tutorial prepares you for.
5. Rate Limiting Without Redis Is Fine (For Now)
Every API endpoint has rate limiting. I used an in-memory sliding window approach rather than reaching for Redis immediately. For a single-instance deployment, it works perfectly. The code has a clear path to Redis when horizontal scaling becomes necessary. Don't over-engineer before you have users.
What's Next
- Smarter album generation (AI-created auto-albums based on events, people, and themes)
- Shared albums with granular permissions
- Natural language advanced search ("show me photos from trips to Japan where it was raining")
The Takeaway
AI makes genuinely useful features possible for solo developers that would have required a team just two years ago. Vision models, vector search, natural language understanding — these used to be Big Tech exclusives. Now you can wire them together over a few weekends.
The key insight: don't sell the AI, sell what the AI enables. Users don't care about embedding vectors or vision-language models. They care about finding their photos in two seconds instead of twenty minutes. Build for that experience, and the technology is your secret weapon, not your sales pitch.
If you're building AI-powered products or want to discuss the stack, reach out via the contact page on the app. I'd love to hear what you're working on.
SOCIAL SHARE CARD GENERATOR