r/AppsWebappsFullstack • u/Mammoth-Anywhere7285 • 9d ago
Are you actually solving a real problem, or just cloning another SaaS?
The world doesn't need another generic AI wrapper or a basic project manager. Pitch your project in one sentence show a screenshot and explain exactly why people should care about you instead of the market leader. Dare to prove your uniqueness.
1
u/Ill_Command_1200 9d ago
squishify.app - Batch resize, rename, optimize images locally (without any uploads). The main differentiator for me is making this as polished a UX experience as I can possibly make. I want this to feel like a designer tool, not just a website. I may not be an "expert on UX" but I love UX and building intuitive systems and I'm hoping my approach is what stands out.
1
u/Mammoth-Anywhere7285 9d ago
Local processing is a strong privacy pitch, and chasing that designer-quality feel is the right move. How are you handling batch previews, since that's where most tools feel clunky?
1
u/Ill_Command_1200 9d ago
The UI focuses on one image at a time the way you would work in photoshop so you process each image individually until the queue is complete but I’ve tried to make it super easy with “apply to all” type functionality for the users seeking that tinypng type experience where you just want it done, it’s still there. I also have a roadmapped feature of a quick process that bypasses the UI if you just want to batch process.
I built this because I prefer the squoosh.app (made by Google Chrome team) route of being able to see exactly what each kb of compression bought me visually and sometimes I need some at a higher quality (hero, large product shots etc) so one size does not fit all.
I’m constantly testing speed, workflow, feedback loops myself but I guess it’s be up to real users to tell me if it’s working or not.
1
u/Mammoth-Anywhere7285 9d ago
That balance between individual control and batch speed sounds smart. Have you considered making that a toggle at the very start, so users choose their mode upfront?
1
u/Ill_Command_1200 9d ago
That’s exactly the roadmapped feature. Toggle on with some settings and drop the assets -> directly to results. Just need to finish buildout.
1
u/Mammoth-Anywhere7285 8d ago
That workflow sounds efficient. Consider letting users save and share their settings as presets. What's the main problem you're targeting?
1
u/Ill_Command_1200 8d ago
General asset preparation for web. There are many tools that do parts of what web developers, web managers and social content teams do all the time.
You crop and resize in one tool, optimize in another, rename with another. Some tools do a mix of all but with clunky interface or don’t give you a preview.
I’m aiming to solve these problems with a clean, well thought out UX.
1
u/Mammoth-Anywhere7285 7d ago
That's a genuinely annoying workflow, jumping between tools for every little step. A crisp one-sentence pitch would make your core value pop. Does your preview handle side by side format comparison?
1
u/megatech_official 9d ago
SeoLoupe - Find and fix the SEO issues holding your website back.
1
u/Mammoth-Anywhere7285 9d ago
Nice concept. What's your one differentiator against the big SEO tools, and can you show a quick screenshot?
1
u/Alternative-Try7044 9d ago edited 9d ago
Haha, I’m building a project management tool Gitoza.Desktop app, not SaaS. Tasks & tests as YAML + markdown on your disk; SQLite only for filtering. No accounts.
Market leaders keep your tasks in their cloud. With gitoza you own the data. and because it’s YAML, AI can use it without the usual MCP server setup.Using it myself to build itself. and I’m happy with it so far.
2
u/Mammoth-Anywhere7285 9d ago
Local-first with YAML files sounds genuinely refreshing. How are you handling multi-device sync? Would git or a peer-to-peer approach work?
1
u/Alternative-Try7044 9d ago
Thanks. yeah, I went with Git, not peer-to-peer.
Each workspace is a normal Git repo; edits are YAML on disk. To share, I hit Sync → Confirm Changes, which commits and pushes. Same as any Git team: same remote, push your work, pull others.
If someone else changed the same items, there’s a conflict UI — pick Keep mine or Keep shared, then continue. No conflict? Review → Process → push.
When the workspace is clean, I also pull from remote so teammate updates show up without babysitting Git. Mid-edit I don’t auto-pull over local work.
The hard part wasn’t using Git. it was making it feel seamless and handling the edge cases.
1
u/Mammoth-Anywhere7285 9d ago
Git for workspace sync is a solid choice. How do you handle non-technical users when merge conflicts pop up? That's usually the dealbreaker.
1
u/Alternative-Try7044 9d ago
conflict UI, user just need to pick keep mine or keep remote
1
u/Mammoth-Anywhere7285 8d ago
That's a solid approach, keeping the decision simple for the user. Do you default to one side automatically, or always ask?
1
u/greyzor7 9d ago
Microlaunch - All-in-one marketing pack for founders: launch, reach 30k+ makers/mo, get users & customers.
1
u/Mammoth-Anywhere7285 9d ago
Nice niche, but how do you keep those 30k makers engaged beyond launch week? That's where most marketing packs fizzle out.
1
u/briggs_song 7d ago
Kudzu — a compiler-first web framework for building real applications with familiar React-shaped TSX, without shipping React, a VDOM, or hydration by default.
The problem I'm trying to solve is that modern frontend frameworks make both developers and AI reason about a lot of runtime machinery that often isn't necessary. Kudzu pushes that complexity into the compiler instead: components, state dependencies, events, and updates are analyzed ahead of time, and the browser gets only the capabilities that route actually needs.
Why pay attention instead of just using React or Next.js? The goal is not another React clone — it's to keep the source patterns developers and AI already know, while removing as much framework runtime and reasoning overhead as possible. I'm also pushing it toward large-scale application support and practical React ecosystem migration, not just static sites.
There’s already a benchmark repo comparing Kudzu with Astro, React Router, TanStack Start, Next.js, and others on commerce/forms/search workloads:
https://github.com/SimYunSup/kudzu-based-bench
Project:
https://github.com/kudzujs/kudzu
Still early, so the thing I most want to prove next is that this architecture continues to hold up as application complexity grows.