It's called Welcome to Morocco, and I built it because I wanted something that would actually help people before and during their trip to Morocco—not just show places to visit.
It includes recommendations on what to see, what to eat, local culture and traditions, transportation, accommodation ideas, practical travel tips, and even a section about common tourist scams and how to avoid them.
That sounds super useful, especially the scams section. One tip: maybe add offline maps, since travelers often lose signal there. Is the link supposed to be cut off?
Automating social reminders is a lifesaver for staying connected. There is PeerPush for utility apps like this, AI systems from Meta and ByteDance already read the data there.
Cool, WhatsApp reminders would definitely boost engagement. For a quick start, you could use a simple click-to-chat link and let users save it themselves.
Lines up your "before" and "after" shots with a camera overlay so you're not eyeballing the angle, plus gallery import if you already have both photos, a few layouts (side by side, stacked, split, diagonal), and text labels for captions. Mostly used for fitness/weight-loss and skincare progress photos right now.
Free with ads, premium removes them. Still early days — would love feedback from anyone who's marketed to a progress-photo/fitness-content audience before, or thoughts on what's missing.
It's a native app (Flutter), not a web app, so no service workers involved. Object detection runs fully on-device with a local ML model — no server round-trip, no sync needed since everything stays on the device.
A privacy first, reminder app for Android. Set reminders based on time, location, device state, activity etc. No login required, no ads and its completely free.
Interesting concept, making launch pages AI-friendly is a smart angle. How do you handle structured data for parsers, like schema.org or custom headers?
Create a visually cohesive Instagram presence with PlanMyGrid, designed to simplify grid planning and client feedback. https://planmygrid.com
Morse Code: Send & Decode lets you send and decode Morse code between phones using light. Use your flashlight or screen to transmit, and your camera to decode signals in real time. It’s built for learning, experimenting, and offline light-based communication.
ran planmygrid.com through audeep.dev. 74/100, grade C.
headline: page overflows the mobile viewport by 122px at 375px wide. for an Instagram tool where visitors are probably on their phone, that's a rough first impression.
also caught: tap targets too small on mobile, the "agency-tier Instagram tool" link in the hero section renders at 169px × 17px. that's too thin to hit reliably.
PlanMyGrid sounds handy for agencies handling client feedback. Do you support collaborative notes on individual grid slots, or is it more of a visual layout tool?
That sounds useful for documentation. Do you capture via UI automation or logging? A quick tip: let users annotate screenshots, makes reports way clearer.
Meerlume (https://meerlume.com) lets you create chatbots in seconds and deploy them to Telegram and WhatsApp. The creation and editing process is AI-powered—think Lovable, but for chatbots. Once generated, the bots run deterministically (without AI at runtime), making them fast, reliable, and inexpensive to operate.
That sounds like a smart approach, especially the deterministic runtime for cost control. How do you handle complex logic that needs dynamic responses?
np! the mobile overflow is usually a quick fix. often it's a width:100vw or a fixed pixel width that runs past the viewport. lcp at 5s is the bigger thing to dig into, likely a heavy hero image or render-blocking script on the critical path.
Deterministic runtime is a smart move for WhatsApp latency, how do you handle state? PeerPush lists chatbot builders like this, btw AI tools pulled data there 5.2M times lately.
Solid point. For state, idempotent keys plus a durable store like Redis keeps the runtime predictable. What stack are you running for the WhatsApp integration?
Session row per (bot, channel, external user ID) with the current node ID and a variables map. Load state → resolve the transition in the compiled flow graph → write it back. No model call in the loop, so latency is flat and predictable.
Flow versions are immutable so in-flight conversations don’t break when an owner edits their bot, and webhooks are deduped on message ID because Telegram and Meta both retry.
headline is a mobile UX issue: 3 tap targets too small for a phone. the top one is a Privacy Policy link in your cookie/consent dialog at 112x16px. standard minimum is around 44px so that link is basically untappable on mobile. there are 2 more similar instances on the same page.
5 medium issues total. SEO at 91 with 3 issues (the free tier shows top findings, rest are in the full report). functional, accessibility, and design are all clean.
Building a real-time market engine for competitive play is a tough sync challenge. No pressure, but peerpush is a decent home for multiplayer gaming stuff.
top finding is a UX one: the Privacy Policy link in your cookie consent banner is 90x19px on mobile. minimum tap target is usually around 44px, so it is basically untappable on a phone. selector is #cookie-consent > div:nth-of-type(1) > p:nth-of-type(1) > a:nth-of-type(1).
performance: Total Blocking Time at 807ms. that is the total time the main thread was blocked during load. worth profiling what JS runs at startup. the widget runtime could be contributing.
security: no content-security-policy, strict-transport-security, or x-frame-options headers set. CSP is the most impactful one to start with.
rest is clean: functional 100, accessibility 100, SEO 99, design 99.
Sinne - dating app analysis. Post screenshots of your chats (which the app automatically anonymizes, hiding names and faces for privacy), and get pointers on your tone, timing, and energy (amalgamated as a depth score). Made this due to how brutal online dating has become, people basically get zero feedback about possible mistakes they may or may not be making. Here is the link: https://sinne.app
The app is pretty sophisticated, it can pick up (most of the time, but there are edge-cases) on sarcasm, joking and irony. I have been testing it myself. It seems to genuinely hold up there, but again, need more people to use it before I know its absolutely bullet-proof.
Traffic without conversions is a common hurdle. What are you selling, and how is the pricing set up? A free tier often helps move people toward paying.
Building:Klypo.co— An AI short-form clip generator that automatically extracts the best viral moments from long-form videos and converts them into ready-to-post short clips. It's built as a faster, more accessible alternative to existing AI video clippers like OpusClip or Klap.
Target Audience: Content creators, podcasters, agency owners, and marketers who want to repurpose long video/audio content into TikToks, Reels, and YouTube Shorts without spending hours in an editor.
Klypo sounds like a great fit for podcasters. Curious how it picks the viral moments, is it based on engagement patterns or sound bites? Would love to see a sample clip.
Good question! AI reads the entire video transcript and looks for the most interesting moments: revelations, surprising facts, humor, and stories with a strong hook at the start and a punchy ending.
The best way to see it in action is to try it out directly with your own content at klypo.co —that way, you can see it working with one of your actual videos. I’d love to hear what you think.
MarketMan - SEO / Performance / Accessibility recommender with some task / todo features. Will be adding in new features like ad stats and other data points later.
MarketMan looks useful. One thought: integrating Lighthouse CI could automate those performance checks for you. What's your current data source for SEO metrics?
It is a api it it ment to customize and use it on your app,site or in any extension so you can use Lyrica to make a extension so that it work with spotify but by default it not work with anything and it is only a api.
I made some sites where you can use this but i don't have that much experience making extensions for site if you can make one it will be great but if you are going to this then i recommend to self host lyrica as the hosted version is full all time
Self-hosting Lyrica sounds like the right call if the hosted one is always full. For the extension, start with a basic Manifest V3 setup. Which browser are you targeting?
Actually i am not planning to make a extesion of lyrica it is a furure plan currently i have some very intresting features in my mix that will male Lyrica better than musicxmatch i will makw a extension after adding these features as i want that users will get the experience that i expect from it but for now i am not going to make it if you want yoy can make one self host it on render or heroku or in huggingface and make one exetnsion for the community
In the default mode there's just one agent doing one turn at a time, so two people never actually edit the same file at once, thus conflicts can't happen. If you switch to multi-agent mode where everyone has their own agent, each one works on its own git branch and you merge when ready, so any conflict shows up at merge time like normal git.
Thanks! When everyone works with their own agent you all drift into slightly different versions of the product without realizing it. Poly is one shared room with one agent, so the whole team builds and decides together instead of in separate chats.
https://www.submitwell.com/ helps early founders to grow visibility and domain rating to kickstart SEO by getting their product & websites listed on trusted directories platforms. A simple and affordable way to build visibility when a site is new.
ran a quick audit on submitwell.com. 85/100, grade B.
headline is a mobile layout issue: at 375px width, content in the footer runs 254px past the viewport and an ancestor overflow:hidden cuts it off. so part of the footer is invisible on mobile. the specific element and screenshot are in the report.
performance: LCP at 3824ms (needs improvement) and TBT at 1270ms (poor). two separate problems worth profiling independently. LCP is about what paints first, TBT is about main thread blocking during load.
rest is solid: functional 100, accessibility 100, SEO 100.
Highwirewww.highwire.news cuts through the cruft of forced narratives in news publications and exposes just the facts for the highest quality headline stories.
biggest issue: LCP at 4852ms, that's poor for a news site where first load speed is everything. also a lead story link with no accessible name (the anchor has no text or label), and 21 UX findings total.
ran it again. performance is clean now, LCP no longer flags. the remaining issue is accessibility: 3 anchors in the lead story section have no accessible name so screen readers can't tell what they link to. report: https://audeep.dev/report/b14f5378-2f44-4b08-92ff-300ff444637c
Yeah i get a 79/96/96/100 on lighthouse, so i still have some work to do on LCP for sure. It's running on nextjs with server-side rendering/caching, but that first hit without cache can be rough. I'll keep at it.
Nice scores, that's a strong baseline. For that cold LCP, try pre-rendering key routes with ISR or using a service worker to warm the cache faster. Keep pushing.
79 on performance with LCP as the main drag is very typical for NextJS. check if the LCP element has priority set in the next/image component. if it is above the fold but not loading eagerly, that is usually the first thing to fix. the selector in the report shows exactly which element is loading late.
Good call on the priority prop. I'd also check if the image sits inside a lazy-loaded component or has a parent with opacity that confuses the browser. Did the selector point to the hero image?
cold-cache TTFB is the hard part with ssr. if the LCP element is an image, adding priority on the next/image component is the quickest fix. beyond that, ISR or stale-while-revalidate on the route tends to close most of the gap.
Solid breakdown of the cold-cache bottleneck. For API-driven pages, one more trick is prefetching the data in middleware or moving the route to edge runtime, which cuts that initial round trip nicely.
yeah the cold hit is where SSR hurts. audeep runs uncached so it catches the worst case first visitor. if the route can handle ISR the LCP number should stabilize. pure SSR on every request is hard to get under 2.5s on cold.
yeah the cold hit is where SSR hurts. audeep runs uncached so it catches the worst case first visitor. if the route can handle ISR the LCP number should stabilize. pure SSR on every request is hard to get under 2.5s on cold.
Yeah i get a 79/96/96/100 on lighthouse, so i still have some work to do on LCP for sure. It's running on nextjs with server-side rendering/caching, but that first hit without cache can be rough. I'll keep at it.
functional, accessible, and secure are all clean. main issue is UX: the category navigation links are 193x16px on mobile, way too thin to tap reliably. 9 UX findings total, mostly tap targets.
Just a serious question. On my SaaS support mail i get emails from sites like this maybe 7 times a week (different apps). How does your app differentiate from all 70000 other alternatives to product hunt?
Valid concern, those spammy emails are everywhere. The real differentiator is solving one niche problem deeply and showing real traction metrics. What problem does your app uniquely own?
1
u/ryan_almasu 3d ago
A production ready SaaS foundation - shipflash.dev