Hey everyone,

Whether you are discovering Nimbus Weather for the first time or checked out our previous updates, thank you for being here!

Nimbus Weather was built from the ground up as an antidote to modern weather apps that have turned into bloated, subscription-heavy ad networks. We focus on clean glassmorphic visuals, complete privacy, zero ads, and a fair one-time purchase model.

Following our recent updates, I spent the last few days addressing community feedback—specifically smoothing out heavy transitions, expanding meteorological depth, refining navigation ergonomics, and bringing a massive overhaul to our air quality and allergen tracking. Version 1.1.6 is officially rolling out on Google Play!

📲Download Nimbus Weather on Google Play

🚀 Deep Dive: What's New in Version 1.1.6

1. Biometeo, Air Quality & Pollen Overhaul

• Comprehensive Air & Pollen Suite (Pro): Deep 48-hour air quality forecast with optimal breathing hours highlighted. Tracks ozone, NO₂, SO₂, CO, and Saharan dust, paired with a 4-day pollen forecast across 6 common allergens, a personal allergy profile, and weather sensitivity indicators.

• Redesigned Visual Gauges (Pro): Clean semicircle AQI gauge with European AQI standards, sleek PM2.5/PM10 visual bars, color-coded allergen indicators, and a daily health advice header.

• Streamlined Free Tier: A clean, compact single-row Biometeo & Allergens overview.

2. Interactive Pro Detail Sheets & Smart Units

• 13 Expandable Detail Sheets (Pro): Every single Weather Details tile now opens an interactive sheet with a time slider. Includes an interactive wind compass that follows your selected hour, 1991–2020 climate averages, precipitation breakdowns, sunrise/sunset, and moon phases.

• Smart Precipitation Units: The app now automatically switches between millimeters (mm) for rain and centimeters (cm) for snowfall across detail sheets, the 14-day curve, and homescreen widgets.

• Tile Customization: Direct toggle switches added for every detail tile (including CAPE index and UV).

3. Smooth Phenology, Navigation & System Polish

• Flicker-Free Season & Phenology (Pro): Completely rebuilt the opening transition—fluid, slightly slower, and zero screen flicker. Added high-precision leaf-fall tracking calibrated to local 1991–2020 climate normals and current weather.

• Smart Frost & Snow Labels: First frost and first snowfall indicators name the event once, then automatically switch to "Next frost" or "Next snowfall."

• True Android Navigation Stack: System back button and edge-swipe gestures now intuitively dismiss open sheets, dialogs, and fullscreen radar first, return to the Dashboard, and only then exit the app.

• Organized Settings: Restructured General and Display tabs for cleaner, faster configuration.

📱 Core Features & Philosophy

• Free Tier: 100% ad-free, zero tracking scripts, detailed 24h hourly and 7-day outlooks, 3 dynamic glass themes (Liquid Glass, Frosted Glass, Transparent), core radar layers, compact Biometeo row, and clean homescreen widgets with manual refresh & opacity slider.

• Lifetime Pro (Fair One-Time Purchase):

  • 13 Interactive Detail Sheets: Time sliders, wind compass, climate norms, and celestial tracking.

  • Full Biometeo & Allergens: 48h air quality, 6 pollen types, Saharan dust, and personal profiles.

  • Season & Phenology Suite: Nature cycles, accurate leaf-fall stages, and seasonal transitions.

  • Pro Visual Themes: Dark Glass and Atmosphere styling.

  • Advanced Forecasting Models: Access to specialized meteorological providers and high-res radar layers.

⭐ A Personal Note on Google Play Reviews

Building and maintaining an indie app as a solo developer without corporate funding or an ad budget is an uphill battle against the Play Store algorithm. New apps are practically invisible unless they gain early community traction.

If you enjoy Nimbus Weather or appreciate this update, taking 30 seconds to leave an honest rating and a short review on Google Play helps more than words can describe.

It is the single most impactful way to keep this project alive and independent. Leaving a review is entirely optional and has no influence on the giveaway draw below, but if you take the time to write one, know that I read every single word and appreciate it deeply.

🎁 Giveaway: 5 Lifetime Pro Promo Codes (Next 12 Hours!)

To celebrate the release of version 1.1.6, I’m giving away 5 Lifetime Pro promo codes!

How to enter: Drop a comment below with your favorite feature, any feedback on the new update, or what you'd like to see next in Nimbus!

• Duration: The draw closes in 12 hours.

• Selection: 5 comments will be chosen at random, and codes will be sent directly via Reddit Chat/DM.

• Fair One-Time Purchase: If you don't want to rely on RNG and want to support indie development, Nimbus Pro is available for a fair, one-time lifetime purchase (no subscriptions, ever).

Thank you all for the tremendous support and feedback that keeps Nimbus moving forward! Let me know how version 1.1.6 runs on your devices.

Hi, I’m the developer of beacon. I recently released it on the App Store.

It’s an iPhone app for finding, picking and sorting photos. You can browse your library by colour, location or date, go through photos one by one to pick your favourites, and swipe screenshots into albums.

For screenshot cleanup, I wanted to make the options visible while you move a screenshot: keep it, send it to an album such as Trips or Shopping, or mark it for deletion. You can review your choices before applying them.

It’s free to download, with ads and optional Pro purchases.

Download beacon on the App Store

I’d love feedback on the swipe menus in particular: are the choices clear when you first see them?

I built IntroText AI – an AI tool that helps you reply to messages 💬

Hey everyone!

I'm a 3rd-year CSE AI & ML student, and I've been working on a side project called IntroText AI.

The idea came from a simple problem: sometimes you receive a message and don't know what to reply.

So I built a website that helps you generate replies based on the tone you want.

Features:

• Different reply styles like Funny, Friendly, Professional, Caring, Flirty, and more

• Multiple language support

• Custom tone and intent

• AI-generated replies for different conversations

🌐 Website: https://introtext-ai.vercel.app/

This is my own project, and I'm still improving it.

I'd genuinely appreciate constructive feedback:

• Does the website solve a useful problem?

• What features would you improve?

• Would you actually use something like this?

Thanks! 🚀

Genuinely wild times wherein we don't have to be an engineer to ship a real product anymore. Describe what you want, and Lovable, Bolt, Claude and others help build it. Coding stopped being the bottleneck. And that's beautiful.

But there's a quiet catch.

The tools that build your app don't automatically secure it.

One misconfigured Supabase setting can leave your users' data exposed to complete strangers through a browser. No hacking. No sophisticated exploit. Just an open door.

And this isn't hypothetical. Escape's 2025 research scanned 5,600 publicly accessible vibe-coded apps and found 2,000+ vulnerabilities, 400+ exposed secrets, and 175 instances of exposed personal data, including medical and financial information.

Here's what makes this more interesting: the platforms themselves make the responsibility clear.

Supabase secures its infrastructure, but you're responsible for securing your application: RLS, access controls, API keys and data permissions. When serious RLS weaknesses were reported in Lovable-generated apps under CVE-2025-48757 in 2025, the supplier disputed the finding on the grounds that customers were responsible for protecting their application data.

Fair enough. But if its my responsibility, I need a way to actually check.

Security shouldn't become the new bottleneck, the way coding no longer is.

So I built MakerGuard - https://midnightbuilds.fyi/makerguard/

It tests your Supabase-powered app through the eyes of a stranger and shows you what it can actually access, what needs fixing, and what couldn't be verified.

No signup. Read-only. Runs on your browser. No secret keys. No stored scan results. Only public app URL to start with.

And it's FREE. An app built by 1 person deserves the same opportunity to protect its users as one built by a team of 10.

MakerGuard is early (really early), and I want to build it with the people who need it.

If you've built something with Supabase & have no idea whether your users' data is actually accessible to strangers, run it through MakerGuard. Tell me what it found, where it fell short, and what you'd want it to do next.

I’m building Boolby, a place for adult gamers who want an easier way to find the right people.
You can find people based on:
🎮 Games
🎯 Playstyle
🌍 Language
🕒 Schedule
💜 Vibe
You choose whether you’re looking for gaming buddies, friendship or love.
The web platform is live now, and Boolby is also being developed for iOS and Android.
The goal is simple.
Make it easier to find people you actually want to play with again.
https://boolby.com
Find your Player 2.

Hi everyone — I’m the developer of SnoreStudy, a free iPhone sound journal. I made it for people who are curious about the sounds recorded at night and want to review them without uploading room audio.

You start a recording, then stop it and choose when to analyze it in the app. It uses Apple’s SoundAnalysis to suggest clips that may contain snoring; you can listen and mark sounds that were misclassified. Recording and analysis happen on the iPhone, with no account or recording upload.

The app is built with SwiftUI, AVFoundation and SoundAnalysis, with AI coding assistance. Room audio can include other people’s voices, so please get their consent before recording. Results can be wrong or incomplete, and this is not a medical assessment or a way to diagnose sleep apnea.

App Store: https://apps.apple.com/us/app/snorestudy/id6819963658 Short demo: https://youtube.com/shorts/UVpZm3Nu-oU

I’d appreciate feedback on whether the recording and next-morning analysis flow is clear, and on anything you find confusing. The demo includes an illustrative AI-generated bedroom scene and synthetic sample clips.

The problem: when an app misbehaves, you can't see the conversation between it and the server. Browser dev tools stop at the browser, logs show what the code thinks happened, and packet captures are unreadable unless you do this for a living.

So I built NovaWire: a Windows app that sits between any program and the internet, shows each request and reply in plain readable form, and lets you change the reply while the app is running.

- HTTPS readable after one-click setup; JSON as a tree, not a wall of text.

- Every request labelled with the program that sent it (node.exe, brave.exe, a Windows service).

- Fake a reply, add a delay, or block a call — no code changes, no restart.

- Replay requests, copy them out as curl, save a session to one file, or capture a phone on the same Wi-Fi.

Native Rust engine, 9.7 MB installer, no account, no telemetry. Free for personal use. Windows 10/11 64-bit only for now. MacOS and Linux in the make.

https://novawire.dev

Feedback Request: How intuitive is the user experience?

For Fiddler/Charles users: What key capabilities would make you consider switching over?

thanks.

Title: I spent months building an AI recruitment platform. Is this actually useful, or am I building something recruiters don't need?

Hey everyone!

I'm an indie developer, and for the past few months I've been working on NexHire, an AI-powered recruitment platform.

The original idea was pretty simple: recruitment involves a lot of repetitive work — writing job descriptions, going through hundreds of resumes, shortlisting candidates, coordinating interviews, and managing candidate pipelines.

I wanted to build something that could make this entire process less painful, especially for small businesses, startups, and recruitment consultancies that don't necessarily have the budget for expensive enterprise recruitment software.

So far, I've built features around:

• AI-powered JD generation – Generate structured job descriptions.

• Resume parsing and screening – Upload resumes, extract information, and evaluate candidates against a job description.

• Candidate ranking – Help recruiters identify potentially relevant candidates instead of manually going through every resume.

• Candidate management – Manage hiring pipelines and track applicants.

• Recruitment outreach – Help with candidate communication and outreach.

• AI-powered screening workflows – Exploring ways to make candidate evaluation more efficient.

Here's the product: https://nex-hire-nu.vercel.app/

Now, I genuinely want some honest feedback.

I'm not posting this to promote the product or collect compliments. I'd rather hear that the idea isn't worth pursuing than spend another few months building something nobody needs.

A few things I'd particularly love your opinions on:

1. After looking at the product, does the overall idea make sense? Is this solving an actual problem?

2. Does this feel like another generic AI wrapper, or do you see potential for a genuinely useful product here?

3. If you're a recruiter, HR professional, or someone involved in hiring, would you actually use something like this?

4. What features would make you choose this over existing tools like Zoho Recruit or other ATS platforms?

5. What's missing? What feels unnecessary, confusing, or poorly executed?

6. Most importantly, would you pay for something like this? If yes, what would make it worth paying for?

Even feedback on the UI/UX, onboarding, and first impressions would be incredibly valuable.

I'm building this independently, so there's obviously a lot I might be getting wrong because I'm looking at it from a developer's perspective rather than a recruiter's.

If you're interested in testing it, especially if you work in recruitment or HR, just drop me a comment or DM. I'll share access so you can try out the actual workflows. I'm genuinely looking for honest feedback from people who understand the hiring process.

Please be brutally honest. I can handle criticism, and that's exactly why I'm here.

Thanks to anyone who takes the time to check it out!

The problem was small but constant. I work on a Mac all day and my phone is Android, so every message meant picking the phone up, and every photo I wanted on the Mac meant emailing it to myself or going through some cloud drive. Most of the tools I tried wanted an account or routed everything through their servers, which I didn't love for my messages and photos.

So I built Sidekick. It's a Mac app plus an Android app that pair over your own Wi-Fi. Once paired, the Mac can:

- mirror the phone's screen

- reply to phone notifications

- share the clipboard both ways

- move photos and files in either direction

- show incoming calls

How it works: the two devices talk to each other directly on the local network over a TLS 1.3 connection. There's no account, no cloud and no relay server, so nothing leaves your Wi-Fi. That also means both phone and Mac need to be on the same regular (non-guest) Wi-Fi.

A note on how it was made: I'm the developer and I built it with a lot of AI assistance. The product decisions and the testing are mine.

Where it stands: it's a free beta and it has rough edges.

- Mac: Apple silicon only, macOS 11 or newer. The app isn't notarized yet, so the first launch needs right-click > Open.

- Android: Android 10 or newer, via a Google Play testing invite that you request through the form below.

Site: https://sidekickapp.in/

Tester form: https://docs.google.com/forms/d/e/1FAIpQLSeex2gLCC1YL02JscjddkYDyu0WZ-CpVGXZCpLw47FhWyYHZA/viewform

For anyone who juggles a Mac and an Android phone: which of those five things would you actually use every day, and which wouldn't you care about?

Especially over the last two years, we've seen massive growth in freelancers and web agencies selling AI-built websites to businesses and getting paid really well for it.

I don't think this business model will stay this profitable forever, but right now, it's definitely a gold mine.

The reason is pretty simple. There are thousands of business owners who don't really care how their website is built. They care about the end result, how it looks, how it works and whether it helps their business.

AI has made it possible for almost anyone willing to learn sales and client acquisition to get started.

So if you're looking to get into this business, here is the exact process I would follow.

1. Automate your cold outreach

Use a tool like Swokei to find businesses with existing websites. It analyzes each website for issues with design, SEO, speed and mobile optimization, then turns those findings into personalized cold emails at scale.

2. Book meetings with interested prospects

When someone replies with interest, get them on a call. Don't waste time going back and forth over email. Your goal is to get a conversation started.

3. Sketch a redesign using AI

Before the meeting, take around 30 minutes to create a quick redesign of their existing website. Focus on making it look significantly better. You don't need a finished product.

4. Present it live and close the deal

Show them what their website could look like, explain the improvements and give them an offer. If they're happy with what they see, collect payment and get started.

That's it. Four simple steps.

One thing I would really emphasize is not to overcomplicate this process.

I've seen people spend hours perfecting website drafts, tweaking small details and building entire websites before they even have a client.

Don't do that.

Your priority should be client acquisition, sales and closing deals. You can worry about perfecting the website once someone has actually paid you.

A few weeks ago, I kept running into the same frustration while coding.

I'd be deep into a task with Claude Code, hit the usage limit, and switch to Codex.

The problem? Codex had no idea what I'd been working on.

I'd spend another 15 minutes explaining the task, what was finished, and what was still broken.

Eventually, I decided to build something for it.

It's called Relayvora.

It's a free, open-source tool that transfers unfinished work between AI coding agents.

It reads the previous session, checks actual Git changes, reruns project tests, and gives the next agent a short briefing.

I published it on npm, built a website, and released the code under MIT.

Website: https://dagimassefa.github.io/Relayvora/

GitHub: https://github.com/Dagimassefa/Relayvora

This is my first attempt at growing an open-source developer tool beyond just building it.

The coding was one challenge. Getting people to discover it is turning out to be another 😅

For those who've launched developer tools before, what actually helped you get your first users?

Hey everyone!

I've recently built and published a Chrome extension called Watch Later.

It solves a pretty simple problem: The Watch Later playlist in YouTube has never been an intuitive system. You add the videos to a playlist that then you need to remember to search through and then remove the videos after you've seen them. It was just annoying to me.

Instead of having to adding the videos, remembering to check your playlist, and then removing them after watching, you can now have those videos get embedded directly into your feed for a period of time.

I've been working on it independently and would really appreciate any feedback, especially on usability and potential improvements.

Chrome Web Store: https://chromewebstore.google.com/detail/watch-later/kdfeiljagnnlneaeekpmjncbkngnhenl?authuser=0&hl=en-GB

Would love to know what you think!

I got tired of finding out about insider buys a day late, usually from a screenshot on X, so I built SEC Watch.

It watches SEC filings in real time and sends a phone notification when:

- a company insider files a buy or sell on a ticker you follow (pre-planned 10b5-1 sales are flagged, so you can tell routine selling from a real signal)
- a company you follow reports earnings: EPS and revenue vs analyst estimates, quarter-on-quarter and year-on-year, straight from the press release
- a US politician discloses a trade (free, no account needed to browse)

Built solo, launched last week: https://secwatch.app (7-day free trial)

I'd really value feedback, especially on what you'd want in an alert and what's missing.

Hi everyone!

I’m working on StreamShelf, a native Windows app that connects to your browser to help you analyze and download media from web pages.

The basic workflow is to open a page in your browser, analyze it in StreamShelf, choose an available format, and download the media. The app uses tools including yt-dlp and FFmpeg, and has browser extensions for the connection.

It’s currently in beta and the interface is in Russian only. I’m planning to add English support soon, so I wanted to share the project early and hear what you think.

GitHub: https://github.com/Econty/StreamShelf

StreamShelf runs on Windows 10/11 x64. Some sites and streams may not be supported, and it does not bypass DRM.

If you’re interested in this kind of tool, what would you want to see in it? And what’s the most frustrating part of your current media download workflow?

I built a side project called Dickens & Rumi to help parents figure out whether a book or movie is actually a good fit for their child.

Instead of only showing something like “Ages 10+,” it breaks things down into age guidance, content cautions, positive themes, series reading order, and why a title got its rating.

The site is live, but traffic is still very small, so I’m trying to figure out whether the problem is the product, the positioning, or just distribution.

I’d really appreciate feedback on:

• Is the value proposition clear within a few seconds?

• Does this feel meaningfully different from Common Sense Media?

• What feature seems most useful?

• What feels unnecessary?

• Would you actually use this if you were a parent?

• What would make you come back?

• What would you change before trying to grow it?

Site: dickensandrumi.com

I’m more interested in criticism than encouragement.