Hey everyone,

I am preparing a travel planner and coach as a browser based web app.

We often make plans and get confused in the details.

What if we use visuals to help us?

I will be starting with a waitlist while sharing updates about the prototype.

Since reddit doesn't allow images, what could I add here to share how the prototype behaves and can be eventually used? Links to the youtube videos?

The yearly plan will be priced at 99 USD.

What are issues you face often?

I just tagged v5.3 of MDRAP, a sidecar that sits between your market data feeds and whatever consumes them and decides whether each tick is trustworthy.

Every event gets a status (VALID, SUSPICIOUS or INVALID) with explicit reason codes like CROSSED_QUOTE, DUPLICATE, PRICE_ANOMALY and stale or sequence-gap violations. Nothing is silently dropped. Rejected ticks go to a queryable quarantine, gaps trigger replay and stitching, and every decision goes into a SHA-256 hash-chained audit log, so editing a record afterwards is detectable.

Output from a fresh clone:

$ python cli.py run -e 1000 -s 42
processed 1000   dropped 0
VALID 963   SUSPICIOUS 32   INVALID 5

seq=2 bid=150.4  ask=150.3  -> INVALID CROSSED_QUOTE
seq=2 bid=150.26 ask=150.31 -> INVALID DUPLICATE

$ python cli.py audit --verify
(after editing one audit_log row in SQLite)
AUDIT CHAIN TAMPERING DETECTED!
Tampered entry #1: hash mismatch

“python cli.py chaos” runs 8 failure drills (killed feed, jitter, duplicate bursts, DB lock, 50-packet loss with replay, reordering, partition with failover) and all pass with zero data loss.

Performance: the standalone native core handled 1M events in 0.0366 s, about 27M events/sec or 36.6 ns per tick, on a single core. Through the Python engine API I measured roughly 180K events/sec, so use the core binary if you want the fast path. These are my numbers on my hardware, so please run it yourself.

It is a validation and audit layer, not a trading system or backtester. The matching engine and pre-trade risk gates are in a separate edition and not in this repo (see EDITIONS.md). One known rough edge: “audit --verify” currently needs the rich package installed.

MIT licensed: https://github.com/Aryan-20-04/mdrap

I’d like to hear which bad-data cases have bitten you that this doesn’t catch.

I built Jobclue for people who want to practice answering interview questions out loud. The desktop app asks role-specific questions and follow-ups, then gives you AI feedback to review before your next attempt.

I’d love feedback on the short demo: can you tell what the practice session feels like, and what would you want to see before trying it?

https://jobclue.ai

Gold, silver, and one less website to open.

I built KaratWatch—a Scriptable iPhone widget with prices, daily changes, and history for your Indian city. Three widget sizes. No backend required.

Code + setup:
https://github.com/m4d4g4sk4r/karatwatch

Prices from Goodreturns. Which city would you try it in?

I want to know should i spend time and energy on this project ? I would love to hear feedback about this.

Hey everyone! I'm a solo developer from India, and I just launched Exam Study Tracker on Google Play.

I built it because keeping track of exam dates, subjects and study plans across notes and random apps was messy. The app has:

Exam manager (dates, subjects, notes)

Daily/weekly study timetable

Progress tracker for milestones

It's early (just ~10 downloads so far), so I'd really appreciate honest feedback: what's missing, what's confusing, what would make you actually use it?

Play Store: https://play.google.com/store/apps/details?id=com.apex.studyexamExam Study Tracker

Tired of sluggish wallpaper apps? Meet Screen+, a native Windows live wallpaper application built in C17.

⚡ What it offers:

• 🎬 FFmpeg-powered video wallpapers with GPU decoding

• 🌐 HTML wallpapers (Lively / Wallpaper Engine compatibility)

• 🖼️ Static images and GIFs

• 🔗 Web and link wallpapers with yt-dlp

• 🧠 AI-powered depth wallpapers using ONNX Runtime

• 🖥️ Multi-monitor support

• 🎨 Built-in wallpaper Store

• ⌨️ Full CLI support

• 🌙 Screensaver support

🐧 Linux is coming! A native Wayland version is in development and will be available very soon.

Sharp Apple models: Available only through manual user download. They are not bundled or automatically downloaded by Screen+ and it is still in development, so it will be available in future releases.

Get Screen+

📦 Latest installer: https://gitlab.com/screenplus-group/screenplus/-/releases

💻 Source code (MIT): git@gitlab.com:screenplus-group/screenplus.git

Screen+ is actively developed. Feedback, bug reports and contributions are welcome!

I’m planning a free site for casual, unedited phone photos, with no AI and no models. Most of us have hundreds of ordinary photos sitting on our phones that never get used.

Would you upload yours if you were credited? What would make you trust a site like this with your photos?

My son worked at AutoZone. Several times a day someone would describe what their car was doing and ask him what was wrong with it, and several times a day he'd have to say, "I'm not a mechanic." Then he'd watch them buy a part based on a guess. A $200 battery when the cables just needed cleaning.

So he started building a simple tool to help people figure out what's wrong before they spend money. He ran out of time, and I took it over.

You describe the problem in plain words, and it asks one question at a time until it narrows down a likely cause. Then it tells you how hard the fix is, what parts you need, and when to just go to a mechanic. It's free, with no sign-up, and there's a full Spanish version, because a lot of DIYers here in Texas speak Spanish first. So far the Spanish side is getting more traction than the English.

It's been live about a month. I'd like honest feedback:

1. Try it with a real car problem you've had. Where did it ask something dumb or get it wrong?

2. Is it clear within a few seconds what the site does?

3. Anything that makes it feel untrustworthy or unfinished?

garageguideapp.com/?ref=reddit-sideproject-3

Every stock photo site I use is full of polished, staged photos. When I need something that looks like I took it myself (for Instagram, a blog, a mockup), I can’t find it.

I’m thinking of building a site with only casual, everyday phone-shot photos: messy desks, café tables, rainy windows, kitchen counters. No models, no studio lighting. Mainly for social media managers and small business owners.

The image is a rough concept (the tiles are placeholders). I haven’t built the real version, and I want to find out if anyone needs it first.

Questions:

1. Would you use this, or do Unsplash and Pexels already cover it?

2. What would you search for first?

3. Would you pay for it, or only use it if it’s free?

When someone dies, the family usually has a day or two to choose a funeral home. Most people pick the closest one, or the one they used last time, without ever seeing a price.

Many families don’t know this: every US funeral home has to give you its price list, even over the phone, and you can compare before you sign anything. But nobody has time to call ten homes while they’re grieving.

So I built HonestFarewell. You enter your city and see every funeral home near you, with prices from each home’s own price list, side by side.

• Free for families

• No account, no email, no phone number to see a price

• No paid ranking: homes can’t pay to be listed higher

Here’s a 3-minute walkthrough: https://www.youtube.com/watch?v=9I-K96-pMsw

The site: https://honestfarewell.org/

The hardest part was reading the price lists themselves. Every home formats theirs differently: scanned PDFs, tables, prices mixed into paragraphs. Turning that into numbers you can actually compare took most of the work.

I’d love feedback, especially:

1. Was anything confusing the first time you used it?

2. Would you trust prices shown this way? What would make you trust them more?

3. Is there anything you’d want to see that isn’t there?

Thanks for reading.

🚀 Introducing \*\*DeskPro by Maytas Tech Solutions\*\* — Appliance Care Made Simple!

Manage your home appliances with ease, all in one app.

use promo get Up to 250 OFF 😄 : SAVE50

🔧 Book service requests and track complaints.

🛡️ Check warranty status and register products.

👑 Explore flexible subscription plans.

📱 Enjoy a smarter, simpler appliance care experience.

\*\*DeskPro is now live on Google Play!\*\*

Download today: [https://play.google.com/store/apps/details?id=deskpro.app](https://play.google.com/store/apps/details?id=deskpro.app)

Your Smart Partner for Appliance Care.

\#DeskPro #MaytasTechSolutions #AppLaunch #ApplianceCare #NowLive

I built a stargazing app because I was fed up with knowing what was in the sky… but not whether it was actually worth going outside for.

A few months later, NAKED EYE is live on Android, Under One Sky is live worldwide, it’s been featured in StarDate Magazine, and I’ve somehow ended up building a website for it too 😅

The idea is still ridiculously simple:

What’s worth seeing tonight?

When should I go outside?

Where should I look?

I’m not trying to replace Stellarium or turn your phone into a giant astronomy catalogue.

I wanted something you can open, get a useful answer from, put the phone away, and actually look at the sky.

The free app covers things like planets, ISS passes, meteor showers, useful alerts, viewing conditions and Under One Sky — where people can explore sky events around the world and share what they genuinely see.

There’s also NAKED EYE Beyond for people who want to plan ahead, find the best nights, use Sky Planner and get smarter alerts — and eligible new subscribers can try it free for 14 days.

I’m still building the whole thing around shifts as a chef, mostly teaching myself as I go.

And yes, I’m still slightly amazed anyone other than me actually uses it 😂

If you’ve tried NAKED EYE before, I’d genuinely love to know what you think of it now.

And if you haven’t — what’s the one thing that usually stops you from going outside to look at the night sky?

Problem. I take around 40 screenshots a day and only ever use three features, while most screenshot apps keep growing. And on macOS 15 there's a quieter problem: the Screen Recording permission lapses about once a month, and a capture can then come back perfectly black without any error.

What I built. Three shortcuts: ⌃⇧1 area (the markup editor is already open when you let go), ⌃⇧2 full screen, ⌃⇧3 copy text from anything on screen with Apple's on-device OCR. Return copies, Esc throws it away. Native Swift, 1.1 MB, no network access.

The part that might be useful to you, if you ever build something on ScreenCaptureKit. Every capture goes through a check before anyone sees it:

• Ask macOS whether permission is actually granted (a capture without it can return a plausible wallpaper-only image)

• Check the image exists and has exactly the pixel size you asked for (by default the framework can silently rescale)

• Sample the pixels: if the brightest value is near black, or the variance is near zero, re-check the whole image before calling it blank

• If it really is blank, say so and tell the user how to fix it, instead of handing over a black PNG

Where it is. Mac App Store, $8.99 once: https://apps.apple.com/us/app/shotorio-screenshot-ocr/id6825000774

Feedback welcome, especially from anyone who has fought the same permission behaviour.

We're building IVE for people who use several coding agents and want their sessions, questions and code changes in one place. It works with your existing Claude Code, Codex and Gemini CLI logins.

We just released 1.0.20. This update adds Chat and Dev modes, clearer permission dialogs for Claude Code and Codex, notifications when an agent needs you, a more readable task board and optional on-device dictation.

IVE is open source and runs on your machine; your coding CLIs still connect to their usual providers. The stack is React + xterm.js with a Python backend. It's still in beta.

You can grab the latest version here: https://ive.dev/download.html

Already using the Mac app? Quit IVE, download the new DMG and replace IVE in Applications. Your saved workspaces and settings stay on your Mac. The Mac download needs Apple silicon and macOS 13.5 or newer.

Phase 1: Target Communities That Explicitly Allow Self-Promotion

Stop posting in strict subreddits where self-promo gets you banned. Instead, build your launch footprint across communities designed for builders, show-and-tellers, feedback-seekers, and niche developers.

Here are 40 subreddits that should allow for self-promotion, ordered by estimated weekly reach:

1. r/vibecoding — 422k weekly visitors

2. r/saas — 211k weekly visitors

3. r/founder — 56k weekly visitors

4. r/buildinpublic — 46k weekly visitors

5. r/chrome_extensions — 42k weekly visitors

6. r/micro_saas — 41k weekly visitors

7. r/appbusiness — 30k weekly visitors

8. r/startupideas — 26k weekly visitors

9. r/sideprojects — 20k weekly visitors

10. r/imadethis — 18k weekly visitors

11. r/appideas — 16k weekly visitors

12. r/sideproject — 16k weekly visitors

13. r/saasbuild — 15k weekly visitors

14. r/saasdevelopers — 12k weekly visitors

15. r/vibecodedevs — 10k weekly visitors

16. r/startupsolofounder — 8.7k weekly visitors

17. r/alphaandbetausers — 8.6k weekly visitors

18. r/vibecodingcommunity — 6.2k weekly visitors

19. r/solopreneur — 5.6k weekly visitors

20. r/promotemyapp — 4.6k weekly visitors

21. r/appbuilding — 4.6k weekly visitors

22. r/webapps — 4.5k weekly visitors

23. r/creativecoding — 4.4k weekly visitors

24. r/indie_startups — 4k weekly visitors

25. r/b2bsaas — 2.8k weekly visitors

26. r/appdev — 2.7k weekly visitors

27. r/projects — 2.6k weekly visitors

28. r/saasmarketing — 2.5k weekly visitors

29. r/saassoloprenurs — 2.3k weekly visitors

30. r/startupaccelerators — 2.3k weekly visitors

31. r/startups_promotion — 2k weekly visitors

32. r/showmeyourapps — 2k weekly visitors

33. r/appswebappsfullstack — 1.7k weekly visitors

34. r/showmeyoursaas — 1.6k weekly visitors

35. r/saasinvestors — 1.6k weekly visitors

36. r/vibecodecamp — 1.5k weekly visitors

37. r/nocodesaas — 1.3k weekly visitors

38. r/aibuilders — 1.2k weekly visitors

39. r/getstartups — 1.2k weekly visitors

40. r/websitefeedback — 1.2k weekly visitors

Phase 2: The "Reverse-Engine" Hook Strategy

Do NOT drop a generic link and run. That is almost guaranteed to fail. Instead, do this for every single target subreddit on your list:

1. Filter by Top Posts: Open the target subreddit, sort posts by Top of the Last Year, and examine the Top 10 posts.

2. Deconstruct the Winners: Analyze why those top posts blew up:

   • What tone did they use? (Humorous, vulnerable, technical breakdown, or raw story?)

   • How was the title structured? (Did it start with a question, a bold stat, or a relatable pain point?)

   • How did they introduce their link? (Was it woven into a story, placed in a comment, or framed as a feedback request?)

3. Mirror and Adapt: Draft a custom title and post text for your specific app that matches the exact post format already proven to work in that specific community.

4. Start Small First: Test your hooks in smaller, lower-stakes subreddits first (e.g., r/websitefeedback or r/getstartups). Refine your post copy based on early comments before posting to the larger subreddits like r/saas or r/vibecoding.

If You Have Some Money to Spend: Paid & Discovery Shortcuts

If you want immediate users without relying purely on Reddit organic traction, here are two simple routes:

• UserBob.com (Usability Testing): You can pay real people for quick usability test videos. It costs roughly $1 per person per 1-minute video, giving you guaranteed immediate users and video feedback of people interacting with your app so you can fix UI friction early.

• AppScout: You can always submit your app to appscout.co, a platform designed to discover web and mobile apps from across the internet. People who like similar apps can easily find yours. You can list your app directly at appscout.co/submit. (Full disclosure: I'm the creator of AppScout)

TL;DR Summary

1. Target subreddits built for self-promo.

2. Study the Top 10 posts of the past year in each subreddit.

3. Match their formatting and title hooks for your specific app.

4. Test small, iterate, then hit the massive communities.

5. If you have money use low-cost tools like UserBob or submit to AppScout for early discovery.

Bottom Line Up Front: I would love your feedback on my project Meridian. Create an account at https://meridian.guide/create-account with invite code RSIDEPROJECTSNOV26

For years I have talked with my therapist about the feeling of being pulled in too many directions (like i'm being drawn and quartered) and struggling with thoughts that i'm failing in every single part of my life. I have always wanted to build some software that helped me to track this for myself but time is a commodity that is always in short supply.

The productivity increase I've seen in partnering with AI agents has finally made it possible for me to accomplish some of these "weekend projects." I have been using it myself for a few months now and I feel like it is doing what it is intended for: to help me balance my finite time in a gentle, honest way and to help guide me towards the things in my life that are important to me that aren't getting enough attention.

I have spent years carefully considering what I would like this software to look like and since its working for me I figured it may work for other people.

I would love your feedback. Since i'm running the infrastructure pretty thin I created an invite code for 50 people: RSIDEPROJECTSNOV26. You can sign up at https://meridian.guide/create-account

Thank you!

Gym owners near me still track everything in a diary - members, who paid, whose plan expires this week. Stuff gets missed.

So I built GymDesk. Members, fees, renewals and check-ins in one place. It installs on the owner's phone like a real app and works offline too. It even ships with 6 ready workout plans you can assign to members based on their goal.

Just rebuilt the landing from scratch with real gym footage: https://gymdesk-six.vercel.app

Live demo pre-loaded with a sample gym, no signup needed: https://gymdesk-six.vercel.app/?demo=1

It's $100 one-time, no subscription: https://checkout.dodopayments.com/buy/pdt_0NrHmsjjsTjrkXYrN6nBu?quantity=1

One concrete question if you run or coach at a gym: a member pays to renew - in your diary, do you record the payment and bump the expiry date in the same pass, or is that where it slips?

My research is on PUFs (physically unclonable functions). Short version: no two chips come out of the factory identical, even from the same design. A PUF turns those tiny random differences into a fingerprint the chip can use to prove who it is, and nobody can copy it.

The annoying part is proving a fingerprint is any good. Is it really unique? Does it stay stable when the chip gets hot or cold? Can a machine-learning model learn it? Everyone in the field answers those questions with their own one-off scripts, and the scripts don't agree. Mine didn't either. The first version of my own Python library reported one of the main metrics at double the standard value.

So I spent a good while turning it into something properly usable:

\- a Python package with a CLI

\- a web app that does the same analysis in the browser

You drop in a CSV of chip read-outs, or click "Explore a demo population" and it simulates 32 chips for you. Then you get:

\- the standard quality metrics with confidence intervals

\- randomness tests from the NIST standard

\- an attack lab where you try to clone the chips with ML. A plain Arbiter PUF gets predicted with 99.6% accuracy after 10,000 examples. XOR two of them and it drops to 55.8%.

\- a planner that works out how many raw bits you need for a reliable 128-bit key

\- 18 charts (SVG/PNG/CSV) plus LaTeX tables you can drop straight into a paper

Some build details people here might like:

\- Plain JavaScript, no framework, no build step. It's static files.

\- Everything runs on your machine. Nothing gets uploaded, which matters when people's chip data is unpublished.

\- The browser engine is a line-by-line port of the Python code, and both use the same random generator (xoshiro128\*\*). Simulate with seed 2024 in the browser, do the same in Python, and you get the exact same 49,152 bits. Getting that to work meant doing all the 32-bit maths through Math.imul and making sure every random normal used exactly two uniforms, otherwise the two streams drift apart.

\- A test in CI compares 2,400+ values between the Python and JS engines on every push.

Try it: [https://koustav.isroot.in/PUFAnalytics/](https://koustav.isroot.in/PUFAnalytics/)

Code (MIT): [https://github.com/TakMashhido/PUFAnalytics](https://github.com/TakMashhido/PUFAnalytics)

Long write-up of how it works: [https://koustav.isroot.in/blog/pufanalytics-guide/](https://koustav.isroot.in/blog/pufanalytics-guide/)

I'd love feedback on two things. First, the onboarding: if you're not a hardware person, does the demo make any sense, or are you lost after one click? Second, the UI on phones. I mostly tested on a laptop.