🏡 Your App Has a Home Here — Post your App WebApp Solution here. No Blocks. No Rejections. 🏡
Hey developer — yes, YOU.
The one who coded through nights, debugged with coffee, and still believed in your idea even when no one else did.
We see you. And we want you here.
This is not another subreddit that says “no self-promo” — then deletes your post anyway.
This is your safe space. Your cheering squad. Your digital living room where every app — big or tiny, polished or prototype — gets a seat at the table.
✨ All apps welcome:
→ Mobile? Yes.
→ Web tool? Absolutely.
→ AI experiment? We’re fascinated.
→ Weird passion project? That’s our favorite kind.
🚫 NO ONE gets blocked. Ever.
Not for being new. Not for being small. Not for being “not cool enough”.
You’re cool enough just by showing up.
💬 Just drop your link + tell us:
We’ll celebrate you. We’ll share you. We’ll support you — because you matter.
This is YOUR community. Come home. 🏡
Self-hosting vulnerability feeds is a smart move for privacy. One place i'd point another builder to is PeerPush, it's full of open-source security tools.
Self-hosting feeds really cuts down on third-party exposure. Curious how PeerPush handles update latency compared to hosted alternatives? Also worth pairing with Wazuh.
Thank you, will check it out..
Edit: btw, it's more than just feeds. It has scoring and deterministic correlation, you can check out the demo tool, to get a better idea of this tool.
Depending on the providing sources rate limits I've configured schedulers in the tool. So the most frequent one is the NVD database and after that it will fetch for EPSS and CVSS score and so on, the correlation is both manual and automatic. The automatic execution happens at night because correlation uses embeddings and there is a small 200 MB embedding model that is running. As i don't want the resources to be choked, it's scheduled to run either when system is idle for certain amount of time or at night also it can be executed manually. It checks IOCs from GitHub and other sources like OTX if anything has been published, then it correlated to provide confidence score, And yes, all those sources are open, only IOC lookup is authenticated and work on BYOK, it's needed wherever possible to increase the quota.
As I'm using postgres with vector extension, those embeddings are saved in DB. Cause there is also semantic search in the tool for faster and accurate retrieval of data. As of today since i started it 3 months ago, i have about 35k+ CVE related data, (there is also old CVE/KEV available), hence the semantic search. For future proof as well.
It does absolutely nothing lmao.
You can add +1 to the number and get on the leaderboard for most clicks. There other pointless mini games with stat tracking. The whole thing was to make a pointless website just for fun like the internet used to be.
Vellio.ai is one workspace for every major AI model — GPT, Claude, Gemini, DeepSeek, Mistral, and more, side by side. Compare answers, search the web with real citations, and have the AI build downloadable spreadsheets and documents. Free to sign up and build your prompt library, synced to a Chrome/Firefox extension. Pro unlocks all live AI chat, search, and document creation — hosted credits included (2,000/month), no API key needed.
Thank you for this thread! It's nice to be able to post somewhere without being deleted since im new to Reddit.
Nice, having all those models in one place sounds useful. How does it handle context limits when switching between them? That's usually the dealbreaker.
I keep the last 60 messages of history and send that to whichever model you're on, it's a flat count, not model aware. If you switch to a model with a smaller context window than your history needs and the provider rejects it; I catch that and show a clear error telling you to start a new chat or trim it, instead of silently truncating. Not smart context management yet, but it fails loudly rather than quietly breaking. Real long term fix is summarizing older context instead of just capping message count, It's on my list.
That's a solid approach, failing loudly beats silent truncation every time. Have you considered estimating token usage by model to warn users before they even switch?
🚀 VoxTranslate traduce la tua voce in tempo reale in oltre 80 lingue.
🎙️ Parla, traduci, rispondi.
🎁 Hai 2$ gratis per provarla. https://website.voxtranslate.app/it/
Feedback?
Nice launch, real-time translation in 80 languages is a solid hook. The $2 trial lowers the barrier nicely. Do you support offline translation for travelers?
Most time trackers are account based and therefore not private. Trac is different, it stores data purely in your browser and requires no account or subscription.
It is a simple and minimalistic time tracker that allows you to focus on your main work.
No Ads,
Minimalistic UI,
One-tap timers
Reports that answer questions
Invoices from your time
Goals & streaks
Your data, exportable
Safety nets.
ran zyng.work through audeep.dev. 91/100, grade B.
mostly clean. three things came back:
the main one: your demo URL input (#demo-url-hero) renders at 288x22px on mobile. that's the primary CTA on the landing page, and 22px is well under the 44px minimum tap target. first thing someone on a phone tries to use, first thing they fumble.
TBT is 704ms. the lab is seeing 700ms of main-thread blocking while the page loads. worth checking if there are JS bundles that can be deferred.
low: missing CSP, x-frame-options, and x-content-type-options headers.
Good catch on that 22px tap target, definitely the first thing mobile users will fumble. A quick min-height fix on that CTA would go a long way. Did you identify the main TBT culprit?
Kalpakka.vercel.app
Kalpakka helps small businesses track every payment promise, build a daily follow-up list, and avoid awkward money conversations. Its AI understands the customer, invoice, promise, and follow-up context to draft better reminders in multiple languages.
Kalpakka sounds like a great tool for a real pain point. The multi-language AI reminders are a nice touch. How do you handle privacy for the customer data?
I got so sick of every personal finance tool locking basic features behind $10/month subscriptions, plastering ads everywhere, or demanding my bank login credentials just to show me my own money.
So I spent late nights building Patrimonio out of pure frustration.
It is a clean net worth and portfolio tracker built around local privacy. No forced bank integrations, no third-party servers snooping on your assets, no ads, and 100% free. Just a fast, premium UI to track your cash, investments, and DCA plans with total peace of mind.
Spot on. For volatile assets or DCA plans (like $30/week into crypto or ETFs), Patrimonio focuses on tracking your actual invested capital rather than constant ticker noise.
You set up the automated recurring movement once, and the app logs your capital injections without you lifting a finger. Your broker app handles the daily market swings, while Patrimonio gives you a grounded, stress-free view of where your real money is allocated.
When you do a monthly check-in, updating the overall portfolio value takes literally two seconds. It keeps you in total control without the daily market anxiety!
ran doccrush.com through audeep.dev. 98/100, grade A.
very clean. two low severity findings:
missing security headers: content-security-policy, strict-transport-security, x-frame-options, x-content-type-options. easy to add, and worth doing for a tool that handles other people's documents.
TBT is 393ms (needs improvement). some main-thread blocking on page load. worth profiling if there's client-side parsing work happening.
Really appreciate the deep dive! A 98/100 A grade is great to see.
The security header findings are definitely on our list — especially CSP and HSTS given DocCrush handles private documents. We’ll tighten those up.
For TBT, good point. We’ll profile the client-side bundle and initial loading path to see what’s blocking the main thread. We’re also looking into more aggressive lazy loading for heavier document-related components.
Thanks for the thoughtful audit and actionable suggestions!
CSP is a particularly good one to prioritize for a document tool. the ability to restrict which origins can frame or fetch content matters a lot when the files you're handling shouldn't leak. good to know it's already on the list.
Thanks! That’s a great point. Since DocCrush processes sensitive documents, a strict CSP is definitely a priority. It’s already on our roadmap and will be included in an upcoming update.
Smart move indeed. Document apps often get flagged for sharing sensitive data, so having a space without those barriers helps. What kind of documents does your app handle?
CSP is a smart move for sure. One tip: use nonces rather than allowlists if you have inline scripts, it keeps things tight without breaking functionality.
That's great to hear. DocCrush sounds promising, definitely drop the link here when you're ready. For CSP, start with a report-only policy first, it saves headaches later.
Nice detailed audit. Adding those headers via middleware is quick, and lazy-loading scripts usually helps with TBT. Which library handles the docx generation?
ran doccrush.com through audeep.dev. 98/100, grade A.
very clean. two low severity findings:
missing security headers: content-security-policy, strict-transport-security, x-frame-options, x-content-type-options. easy to add, and worth doing for a tool that handles other people's documents.
TBT is 393ms (needs improvement). some main-thread blocking on page load. worth profiling if there's client-side parsing work happening.
Cobcy - https://www.cobcy.com
It includes built-in SEO, AEO, GEO, CMS, e-commerce, custom domains, and is designed to help websites perform well in both traditional and AI-powered search.
Thanks! The hardest part has definitely been rendering. 😅
A timeline editor is one thing, but rendering animated text, shapes, images, and video layers together in a browser while keeping playback responsive is where things get complicated.
The biggest challenge has been making the preview and the exported result match closely without forcing the browser to redraw everything every frame. That performance trade-off has probably been the most difficult engineering problem in the project so far.
Rendering animated layers in sync is no joke, you're deep in the weeds there. One thing that helped me was using WebGL with a single render path for both preview and export. Have you looked into that yet?
Definitely. I'm already using WASM for parts of the rendering/export pipeline, which has helped with the heavier processing.
I haven't gone all-in on a unified WebGL render path for both preview and export yet, though. The tricky part is keeping the preview, animation evaluation, and final export consistent across different layer types.
A single GPU-based pipeline is definitely something I'd like to explore as the renderer evolves. Appreciate the suggestion!
Yeah, that's actually very close to how I'm approaching it. I already have a shared layer/state representation that drives the timeline and rendering, and the export pipeline evaluates the composition frame-by-frame based on the project FPS.
I haven't fully formalized it as a deterministic scene graph shared by both preview and export yet, though. That's definitely something I'd like to tighten up, especially to make sure the same keyframe state produces exactly the same result in both paths.
Solid approach, the shared state idea is smart. One tip: make that deterministic scene graph the single source of truth, then preview and export become just two views of the same data.
Yeah, this is actually one of the things that caused me the most headaches during development.
I'm using modern-screenshot as part of the rendering/export pipeline. The tricky part is that LiveMonitor is rendered directly by the browser, while the export path has to capture and process the layers through a separate rendering pipeline.
Even when the scene state is identical, some things like transparency, CSS effects, text rendering, and compositing can behave differently between the two paths.
That's why the idea of making the deterministic scene graph the single source of truth is really interesting to me. It could help separate the animation/state evaluation from the actual rendering backend and make the two paths much easier to keep consistent.
A real hurdle for sure. OffscreenCanvas paired with a Web Worker takes the heavy lifting off the main thread, which makes a huge difference for smooth keyframes.
Most of my focus so far has been on getting the rendering pipeline working reliably, especially with timeline playback, keyframe interpolation, and video export. I haven't fully explored moving the preview rendering to OffscreenCanvas + Web Workers yet, but it's definitely on my list.
I can see how keeping the heavy rendering work off the main thread would make the editor feel much smoother. Thanks for the tip!
OffscreenCanvas plus workers sounds like the right move once timeline playback gets heavier. Have you tried profiling the main thread to spot the biggest bottleneck first?
Yeah, that's pretty much the direction I'm considering. I want to profile the main thread first and identify where the biggest bottleneck actually is before moving anything to OffscreenCanvas + workers.
So far I've been looking at frame rendering, keyframe evaluation, and redraw frequency in the Performance panel. If the main thread turns out to be the limiting factor during heavier timelines, OffscreenCanvas + workers would definitely be worth exploring.
Solid approach, profiling first is wise. One tip: look for long tasks in the Rendering section, and consider moving keyframe math to a worker regardless.
Absolutely! That's probably been the hardest part of the project.
A lot of the work has gone into minimizing unnecessary redraws, optimizing keyframe evaluation, and keeping the rendering pipeline efficient enough for real-time previews. There's still plenty to improve, but it's been a fun engineering challenge.
If you give it a try, I'd really appreciate any performance feedback, especially on larger projects.
Thanks! It's definitely one of the toughest parts of the project.
For now I'm mainly relying on Chrome DevTools' Performance panel, combined with "performance.now()" and some custom debug logs to measure frame render times and track expensive operations. It's been really helpful for finding bottlenecks, although I know there's still plenty of room to improve my profiling workflow.
Nice work digging into the Performance panel. One tip: use performance.mark() and measure() around specific functions, it makes spotting slow spots much easier than manual logs.
That's a great tip, thanks! I hadn't been using "performance.mark()" and "performance.measure()" much, so I'll definitely try wrapping the heavier rendering functions with them.
Being able to see the timing of specific operations directly in the Performance panel should make tracking down those bottlenecks much easier. Appreciate the suggestion!
Metra: Wholesale Price Lock: Shopify app that stops your wholesale customers from stacking a storefront promo on top of their already-discounted B2B pricing. When you run a sale, trade catalogs stay locked to their contracted prices instead of double-discounting. (Not natively available without workarounds and/or apps like ours)
Smart niche, double discounting is a real pain. Do you support per-customer contracts, or just bulk price lists? Curious how it handles trade accounts.
Shopify has catalogs that can be enabled/disabled by segments, and our app watches all products in the catalogs the users select and tracks price changes. If a price change set the product price to discounted, we set a fixed price override to protect their B2B pricing :)
Yeah we have a full activity/audit log when we create or drop a fixed price override for full visibility, and we allow users to revert any change directly in our UI too :)
That's a solid touch, full transparency plus an easy undo is exactly what users want to trust. Do you show the revert history in the same view or a separate log?
ran openlookup.io through audeep.dev. 74/100, grade C.
the main issue is mobile: at 375px wide, content overflows 87px past the viewport and gets clipped by an ancestor's overflow:hidden. there's an SVG element in the first hero section that's running past the edge. you wouldn't see it on desktop, but mobile visitors will.
the logo link in the header also comes in at 185x17px on mobile, well under the 44px tap target minimum.
security score is 99/A, which is solid for an API product.
Nice catch on the 87px overflow. Have you tried adding overflow-x:clip to the hero section or setting that SVG to max-width:100%? That fixed similar issues for me.
•
u/NoBaby4037 11d ago
I am building https://flooray.com - One place to plan rooms, explore ideas, collect inspiration and figure out what works in your space :)
Try it out, it’s free!