After months of learning Flutter in my spare time, I finally launched my first Android app.
It’s called **Quiet Lines**, an AI-powered journaling app designed to help people reflect on their thoughts, emotions, and daily experiences.
I started this project because I’ve always been interested in mental wellness and self-reflection. What began as a small side project slowly grew into a real product that is now live on Google Play.
Some things I learned along the way:
• Building the app was easier than finding the courage to publish it.
• App Store and Play Store requirements took longer than expected.
• Marketing is much harder than development.
• Getting the first real users feels more exciting than writing new features.
Right now, my focus is learning how to get those first 100 users and understanding what people actually find valuable.
For those who have launched apps or SaaS products:
How did you get your first users?
What marketing channels worked best?
What would you do differently if you were starting today?

Google Play:
https://play.google.com/store/apps/details?id=com.calmjournal.calm\\\_journal\\\_template

I’d love any feedback, advice, or suggestions from the community.

I recently built a tool to streamline the getting your art print ready process. I know there are multiple out there already, but none seemed to tick  the boxes for my needs.

My initial thoughts were to keep it as streamlined as possible, but now I feel I can add some extra features without making it too cluttered as efficiency was always top of mind.

Here it is: www.upratio.art

I’d love some feedback, so if anyone was open to testing it out and providing some, I’ll give you unlimited free access in return.

Much love
Upratio.art

I built KansoGate: a simple app where you start a phone-free session and earn coins for completing it.

I used AI to speed up the building process and FlutterFlow to design and style the app. It is still early, but the core idea works: make staying off your phone feel like a challenge instead of a punishment.

Would love honest feedback:

• Does the coin/reward idea make sense?
• Would you call this a focus app, phone detox app, or anti-scrolling app?
• What would make you actually keep using something like this?

I’m the developer, so feel free to be brutally honest.

https://play.google.com/store/apps/details?id=com.mycompany.zunset&pcampaignid=web_share

slagdock.com

a home for free online browser based games, No account needed to play (unless that game has account settings for persistency purposes to save your progress) Access some new indie developer games by other vibe coders and hard core coders.

always accepting more games

Still a bit stunned typing this. Three months ago I was refreshing Stripe hoping for one sale. Now there's a small but growing group of people paying every month to keep their apps from leaking.

CheckVibe is a security scanner for vibecoded apps shipped fast with AI tools. You paste a URL or hook up a GitHub repo and it surfaces what's leaking: secrets in the frontend, open database rules, missing headers. Two of us, fully bootstrapped, no funding. Three months in and we've done about $7k in gross volume, 200+ all time paying customers, 5k signups. Public Stripe link in case anyone's seen too many fake numbers: https://profile.stripe.com/checkvibedev/ZumatA0Y

A few things that actually worked:

TikTok slideshows have carried us. Aesthetic Pinterest-style backgrounds with tool names overlaid, five slides, no branding on the account. One hit a million views and is still quietly sending signups weeks later. 15 minutes to make. As a 2-person team that can't afford to spend hours on content every day, this format is unreasonably good.

Cold outreach worked, but only the version where I scanned the prospect's app first and DMed them what I found. Generic pitches got ignored. Useful findings got replies almost every time.

Paywall design was a 3x lever. The first version blurred all results, which felt clever and barely converted. Switched to one that just shows the count of critical issues with the actual findings locked. Conversion tripled. Curiosity beats obfuscation.

What nearly killed me was mobile activation tanking compared to desktop and not catching it for weeks. Onboarding had too many steps on small screens. Cut two and the gap basically closed overnight.

If you've shipped something with AI tools and haven't really checked what's exposed, checkvibe.dev runs in 30 seconds. Scan for free, only pay if you have issues. Almost every app I've scanned came back with something.

I got tired of network monitors that look like they were designed for a BBS, so I built flow. It's a real time bandwidth monitor with Braille grid waveforms, spring smoothed numbers, and glowing borders that react to traffic load.

What it does

It shows live download and upload throughput with units that auto scale from B/s up to GB/s. The waveform is a high res Braille grid scrolling at 30fps, and the borders glow brighter as traffic picks up, going from a dark idle state to bright cyan and emerald under load. Numbers are spring interpolated so they glide instead of jumping around. It tracks session peaks, flashing white when you hit a new record, and keeps a running daily total.

There are three views that adapt to your terminal width. Hero is the full dashboard. Compact strips it down to numbers only. Tiny is a single line built for tmux status bars.

Philosophy

If a feature doesn't help you understand your network in under a second, it doesn't make the cut. No CPU panels, no packet counters, no multi pane clutter. Just download and upload throughput, done well.

Usage

flow                        # hero view, auto interface
flow --compact              # numbers only
flow --tiny                 # tmux status bar
flow --json                 # one-shot JSON for scripts
flow --once                 # one-shot plain text

tmux integration

set -g status-right "#(flow --tiny --no-color)"
set -g status-interval 1

Install

go install github.com/programmersd21/flow/cmd/flow@latest

or AUR:

yay -S flow-network-monitor-bin

or homebrew:

brew install programmersd21/flow/flow

Pre-built binaries for Linux, macOS, and Windows (amd64/arm64) are on the releases page.

It works with zero config out of the box. If you want to tweak the refresh rate, history length, or units, there's an optional TOML config at ~/.config/flow/config.toml.

Platform support

It runs on Linux (/proc/net/dev), macOS (sysctl), and Windows (GetIfTable2, no admin needed). Idle CPU stays under 1%.

Links

Source and demo: https://github.com/programmersd21/flow

---

Would love feedback, especially on the tiny/tmux mode. Curious if the info density is right for people running it in a status bar all day.

https://github.com/ad-repo/nullplayer/releases/tag/0.27.0

# one-time configuration 
brew tap ad-repo/nullplayer 

brew install --cask ad-repo/nullplayer/nullplayer 

or if already installed manually
brew install --cask --force ad-repo/nullplayer/nullplayer 

To upgrade to a new release: 
brew update 
brew upgrade --cask ad-repo/nullplayer/nullplayer

New Features

• Compact Window adds a free-floating mini player — the Windows menu and main-window context menu now include Compact Window, which uses the same compact Library Browser mini-player as Compact Mode but keeps NullPlayer as a regular Dock/menu-bar app. It hides only the main window, leaves Playlist/EQ/Spectrum/Library/visualization windows where they are, uses normal window level unless Always on Top is enabled, can be dragged from both the player bar and browser area, remembers its frame, and restores across launches.
• Balance control added to Playback menu — the Playback options now include a Balance submenu with a slider and common left/center/right presets, giving modern UI and menu-only workflows access to stereo balance without adding more controls to the player face.

Improvements

• Modern and Metal UI now use a modern system font — the retro low-fi bitmap font (Departure Mono) has been replaced throughout the Modern and Metal windows — Library tabs and headers, the main window, playlist, EQ, and spectrum — with the crisp macOS system font. Time and track digits stay monospaced so they don't jitter. Skins that ship their own custom font still render it as before.
• License and branding terms clarified — the project license notice and README now state GPL-3.0-only distribution terms and clarify that modified distributions must not reuse the NullPlayer name, icon, logo, bundle identity, or other branding without permission.
• Compact Mode player bar reads like the main window — in Modern and Metal, the Compact Mode display now splits into two distinct LCD "windows" with a padded gap: a single elapsed/remaining time counter on the left and the scrolling track title on the right (previously the title sat left with a cramped "elapsed / total" reading pinned to the right). The counter matches the title's size and weight, and the transport buttons are slightly larger.
• Larger Library tab and control fonts — the Library Browser's tab labels and control text render at a slightly larger size in non-compact mode for better legibility. Compact Mode is unchanged.

Changes

• Window shade mode removed — double-clicking a window's title bar no longer collapses it to a title-bar-only strip ("windowshade"). This legacy Winamp feature was the source of recurring layout glitches when combined with Large UI, Compact Mode, and live UI-mode switching; removing it makes window sizing and position memory behave consistently across every window in Classic, Modern, and Metal.
• Library source menu lists only sources — the Library Browser's source picker no longer injects local-library settings ("Manage Folders…" and the "Clear Local Library" submenu) when the local source is active. Those are settings, not sources, and already live in the Library menu-bar item, so the source menu now lists sources only.

Bug Fixes

• Metal skin transport icons are now fully filled — the previous/next (and eject) icons in the Metal finishes no longer show a stray light vertical line: the icon bars now draw in the same transport-button color as the rest of the glyph instead of the skin's light primary color.
• Plex Artists no longer show duplicate same-name rows — the Library Browser now groups Plex artist records with the same display name into one visible artist row in both classic and modern UI. Expanding, playing, or queueing that row still fans out across every underlying Plex ratingKey, so albums and tracks attached to duplicate server-side artist records remain accessible instead of being hidden.
• Compact Mode art ratings fit the small UI — the modern Library Browser's art-view rating stars now shrink in Compact Mode, preventing them from crowding or overlapping the source/library picker row.
• Compact Window no longer reopens the main window after Space switches — returning from another desktop or fullscreen app now focuses the floating compact mini-player instead of treating the hidden main window as something to restore, so Compact Window stays a one-window main-player replacement until you exit it.
• Library window remembers where you put it — after unlocking the connected windows and moving the Library/browser window, it now reopens at the exact position and size you left it — across closing and reopening it (via the menu or the red close button) and across full app restarts, even when it was closed at quit. First-ever opens still dock to the right of the window stack, and the position survives Compact Mode. Playlist, EQ, and Spectrum still intentionally snap back into the column below the main window.
• Classic Large UI toggles instantly — no restart — turning Large UI on or off in the classic skin now resizes the windows in place, matching the modern UI, instead of asking you to relaunch. The player, EQ, playlist, and other windows redraw crisply at the new size (no leftover "ghost" of the old size), and switching between Classic, Modern, and Metal while Large UI is on no longer distorts the new look.
• ProjectM visualizer recovers from a preset that crashes mid-playback — a rare bug inside the MilkDrop preset engine could crash the app while a preset was on screen — including minutes into a track, not just when the preset first appeared. The crash-guard now watches a preset for its entire time on screen (previously only its first frame), so the offending preset is automatically skipped on the next launch and the crash never recurs. Normal quits never flag a good preset.
• Metal playlist and Library highlights are now clearly visible — in Metal skins, the playlist's now-playing track and the Library Browser's selected/expanded row were indicated by text color alone, which several metal finishes render nearly identical to normal rows, so the active row was easy to miss. Both now draw a translucent green backlit-LCD highlight bar (matching the hi-fi display panels) as the cue. The metal playlist's row text is also unified at the Library window's brightness — previously it was dimmer — and the current track no longer recolors to the accent tone that clashed with the new highlight.

Introducing LeakScope, again.

we've been updating it : )

LeakScope is a security scanner built for Supabase applications. Paste your app's public URL, and it checks what an attacker can learn from the outside—from exposed keys and public data access to weak RLS, leaked credentials, and insecure frontend configuration.

We've introduced two scanning modes:

Light Scan — Paste a public app URL to instantly check for exposed keys, public data exposure, leaked credentials, weak RLS, and risky frontend configuration. No account required.

Deep Scan — Authenticate to validate Row Level Security, test BOLA/IDOR, analyze JWT security, and generate detailed reports for real security validation.

Whether you're a solo founder, indie hacker, or vibe coder shipping MVPs at 2 AM, LeakScope gives you a fast way to see what your app is exposing before everyone else does.

1,936 websites scanned.
13,679 security findings identified.

Try it out at leakscope[.]tech

Hello everyone,

Wanted to share LyteNyte Grid, which IMO has some incredibly innovative capabilities when turbocharged with AI.

Building data grids for dashboards, admin panels, internal interfaces, etc. takes a really long time and can be tedious. All this takes away from the time you would much rather spend on your app.

The financial options dashboard above was made with Claude Code using LyteNyte Grid Skills.

The prompt:

Create an options trading dashboard using LyteNyte Grid. data.ts contains options contracts – ticker, type, strike, expiry, IV, and full Greeks.

Enable row grouping by ticker and type, sorting across all columns, and master-detail rows that show the full Greek breakdown when expanded. Use Vite + Shadcn. Dark mode by default.

That was it, one prompt. You can expand it, group it, sort it, filter it. It is also fully accessible.

The reason it works so well is that the grid is declarative and type-safe. AI can verify the result without running the code.

Tokens burned were minimal. Since all the AI had to do was declaratively configure LyteNyte Grid and run tsc to check for errors, there were none.

Other grids are imperative, with heavy abstractions and wrapping layers, making them unreliable for coding agents. If they work, it's usually after 20 prompts, using enough tokens that you might as well just wire it up yourself… or reach your Claude limit.

We will continue work on this, but with LyteNyte Grid, you can now build any type of dashboard for a data-intensive workflow, in literally minutes.

Our API is not opinionated at all, making it really easy to integrate with your favorite UI / charts libraries

Install Skills: npx skills add 1771-Technologies/lytenyte

If you’re unfamiliar with LyteNyte Grid, it’s a 40kb React data grid with 150+ features. I would shamelessly plug its benefits. If you’re interested, they’re listed in the repo.

All our code is available on GitHub: https://github.com/1771-Technologies/lytenyte/commits/main/

I'd love to hear your feedback (maybe showcase your creations?). Feature suggestions and contributions are always welcome.

If you find it useful, please consider leaving a star ⭐ on GitHub to help us grow!

GitHub

Live Demo

every time I built something w/ cursor or claude it came out looking like ai slop (fable 5 just kills credits, others just don't get the "it" feeling)

there's a bunch of really good design references for dashboard ui but I really like landing pages, so i made this tool for myself

if you put uiscanner.com/ in front of any public link, it pulls the site's real design tokens, color roles, type scale, spacing, radii, motion, and does a visual ai pass for a section-by-section breakdown that outputs a build prompt you can paste into your agent

(there's also an mcp/cli if you want to use directly, the webapp side is a library of all ur scans)

free to try, 5 scans a month if u want to try for yourself! (i added pricing so people don't wipe my ai usage lol)

lmk ur thoughts! feedback super appreciated

link: uiscanner.com

Your mouse is slowing you down.

Every time your hand leaves the keyboard, you lose focus.

I switched to a keyboard-only workflow on macOS, and it's surprisingly addictive. The app is made using Swift, and it is created with the help of AI.

Try it yourself:

👉 https://github.com/bhavesh164/mouseless

You'll wonder why you ever reached for a mouse.

Note: This app is made with the help of LLM (AI)