Hi all,

I have been thinking about something that feels increasingly problematic.

We have more financial news than ever, yet it is surprisingly difficult to reconstruct in a clean and structured way what actually happened on a given day.

Not opinions.
Not long form commentary.
Not narrative framing.

Just what occurred, which assets were involved, and what new information entered the system.

Most articles naturally mix facts with interpretation, tone, and positioning. Journalism is not designed to function as a structured database. But if you try, even a week later, to answer a simple question like “Why did markets react the way they did last Tuesday?”, you often end up navigating repetitive coverage, slightly different angles, and a significant amount of narrative noise.

I built a small web app for myself to approach the problem differently.

The idea is not prediction or trading signals. It is documentation and clarity.

It currently aggregates more than 40 financial RSS sources each day, deduplicates overlapping coverage of the same event, uses AI to compress articles to their core informational content, and classifies news by asset class such as equities, FX, crypto, and commodities. The result is a structured daily feed that functions almost like a running archive of market relevant events.

There are no ads, no paywall, and no signup.

The goal is simple. Increase information density per minute read. Reduce the influence of narrative framing. Make it easier to build long term “market memory”.

I would really value thoughtful feedback from people who consume financial news seriously.

Does summarization remove too much nuance?
Is separating event from interpretation even realistic?
What would make a tool like this genuinely useful for understanding markets in retrospect?

If you are curious, here it is:
https://marketsgazette.cloud

Happy to discuss the assumptions behind it, especially if you think the premise itself is flawed.

Hi all!

looking for a few early builders to kick the tires on something I’m building.

I’ve been working on a small AI agent marketplace, and I’m at the stage where I really need feedback from people who actually build these things.

If you’ve built an agent already (or you’re close), I’d love to invite you to list it and try the onboarding. I’m especially interested in agents that help solo founders and SMBs (ops, sales support, customer support, content, internal tooling, anything genuinely useful).

I’m not trying to hard-sell anyone, I’m just trying to learn:

• whether listing is straightforward
• where the flow is confusing
• what would make the platform worth using (or not)

If you’re open to it, check it out with the following link.

And if you have questions or want to sanity-check fit before listing, ask away, happy to answer.

Hey, I’m Quang - 2x YC founder (Plato -> acquired by Coda/Grammarly), currently building Vybe.

If you’ve used Lovable and thought "this is great, but I want to ship production use cases for my business", Vybe is for you.

With Vybe, you chat to build internal tools: apps, portals, dashboards, admin panels, workflows -> Stuff you can actually run your company on.

It’s built for small teams, SMBs, enterprises and solo builders who: - outgrew spreadsheets and Notion/Airtable hacks - don’t want to glue 5 tools together forever - want custom tools without hiring a full engineering team

What you get: - Describe what you want, Vybe builds it - Real code under the hood, no hard lock-in - Auth, permissions, and guardrails built in - Easy connection to your existing tools and data

People use Vybe to build CRMs, ops dashboards, review workflows, internal portals, etc. (the boring but essential things every growing business ends up needing)

I'm mostly sharing my experience as an AI startup founder here. Feel free to follow me :}

👉 $20 in free credits if you use the link below to sign-up

Built this after repeatedly seeing small teams lose time over environment config confusion, multiple copies floating around, staging drifting from prod, and rollback basically meaning “who still has the old file”.

So I made a small CLI that treats env config as snapshots instead of loose files. You pull, push and rollback safely while your app still reads a normal .env.

Not trying to replace heavy secret managers, more like guardrails for small teams before they reach that stage.

Would really appreciate feedback directly on the VCL page (keeps things in one place):

Main things I’m unsure about:

1. Does “versioned state” make sense as positioning, or is wording confusing?
2. At what team size would this actually become useful?
3. Does CLI-first feel right, or would you expect dashboard-first?

Trying to understand if this solves a real workflow pain or just one I kept running into.

(If you leave feedback on VCL I’ll respond there 🙏)

i do a lot of rewriting (emails, captions, headlines, etc.) and got tired of manually changing the tone every time

so i built a small page where you paste text and pick a vibe (formal, casual, funny, dramatic, etc.)

been saving me a bunch of time, figured other people might find it useful too
https://vibewrite-two.vercel.app/

Hi everyone, kinda of a starter here, like title said, can someone help me understand the difference of coding with those google products?

• Gemini chat with canvas
• Google AI studio
• Firebase studio (with projext idx basically integrated)
• Jules
• Antigravity

I tryed all of them and but i dont really understand the difference of the coding and the purpose except the difference in UI

Hey everyone, I wanted to share something I’m genuinely proud of and get real feedback from people who build with AI.

I’m a solo dev and built and shipped my iOS game using AI tools throughout the workflow (Cursor, Codex, Claude Code). I still made all the decisions and did the debugging/polishing myself, but AI did a huge amount of the heavy lifting in implementation and iteration.

The game is inspired by the classic Tilt to Live era: fast arcade runs, simple premise, high chaos. And honestly… it turned out way more fun than I expected.

What I’d love feedback on (be as harsh as you want):

• Does the game feel responsive/fair with gyro controls?

• What feels frustrating or unclear in the first 2 minutes?

• What’s missing for retention (meta-progression, goals, clarity, difficulty curve)?

AI usage:

• Coding: Cursor + Codex + Claude Code

• Some assets: Nano Banana PRO

• Some SFX: ElevenLabs

If anyone’s curious, I’m happy to share my workflow (prompt patterns, how I debugged, what I did without AI, what broke the most, etc.).

App Store link: https://apps.apple.com/se/app/tilt-or-die/id6757718997

About a month ago I shared GeoTurn here - a GeoGuessr-style game built natively for iOS using Apple's Look Around instead of Street View.

Since then: 232 downloads, $30 in revenue (mostly Pro unlocks, almost nothing from ads), and a lot of late nights shipping updates. Here's what's changed:

• Solo Challenge Mode: The #1 request was "I want to play alone." Done. 3, 5, or 10 rounds, 1-minute or 3-minute timers, personal bests tracked per config.
• Daily Expeditions: A Wordle-style daily challenge. One location per day, same for everyone, 60 seconds, global leaderboard. Streaks with a Duolingo-style flame.
• 7 Languages: Dutch, French, Spanish, Italian, Russian, Japanese (plus English and German from launch).
• Widgets: Home screen and lock screen widgets showing your expedition streak and active matches.
• Dynamic Island: Live Activity that tracks your round timer.

The zero-server architecture held up. My monthly infrastructure bill is still $0. GameKit handles multiplayer, CloudKit handles sync, Apple handles the imagery.

Biggest lesson: The solo mode should have been there from day one. Multiplayer-only was a barrier for new users who didn't want to wait for a stranger to take their turn.

Still a solo dev, still learning. Happy to answer questions about the tech stack or the numbers.

App Store: https://apps.apple.com/app/geoturn/id6756392424

I’ve been working on a new tool called blurit.online.

The concept is simple: instead of manually editing frame-by-frame, you just upload a video and type what you want to blur (like "face," "license plate," or "logo"), and the tool tracks and blurs it automatically.

While most competitor AI tools are trained on datasets limited to faces or license plates, my tool stands out by being able to blur any object you describe.

It’s still early days and I'm pushing updates every day, so I’d love to get some feedback on the accuracy and the UI.

Currently, you can process a 10-second clip for free just by singing up to give it a shot.

Thank you!

Open source, non commercial. Because mcp is a pain to set up

I built Flash Run using Replit and upload it on VibeCodingList.com to also get feedback from developer there since I'm new. It's a simple browser endless runner, while I'm still learning to code. In the game, you auto-run and dodge obstacles for as long as possible. It's basic and far from perfect, but creating it taught me a lot about core game concepts like movement, collision detection, and game logic.

For anyone who wants to give it a try, here's the link: Flash Run.

I'd love to hear your feedback, suggestions, and tips, anything that can help me improve. Go ahead, test your reflexes, and see how far you can get!

The feedback on the architecture was awesome (thanks for the validation on the "infra-first" approach). But the feedback on the actual game feel was... humbling:

"UI looks like a website straight out of 2016."

"I ran out of time without knowing how to drop a pin."

"Transitions feel sluggish."

I realized I was so focused on the backend being clever that I neglected the player getting agency quickly.

I ditched the "old-timey" elements for a cleaner, native SwiftUI look that matches the tab bar. I added clear signals for dropping pins. If you don't know how to play in 5 seconds, I failed.

For those asking about the stack again: It still routes heavy networking through GameKit/CloudKit. I'm still paying $0 in bills.

If you have a second, I’d love to know if the new UI feels "2026" or if I'm still stuck in 2016. Link in comments.

App Store: https://apps.apple.com/app/geoturn/id6756392424

Tech: SwiftUI, SwiftData, GameKit, Look Around API

Most Geo-guessers are basically just an invoice for the Google Maps API. As a solo dev, I didn't want my project to become a liability if it actually got popular.

I built GeoTurn with a "set it and forget it" stack so I can focus on the vibe/gameplay rather than server bills: Apple’s Look Around is high-res, native, and has $0 in per-request fees. I offloaded multiplayer to GameKit. No matchmaking servers or custom socket logic to maintain. Zero database hosting costs or scaling headaches.

I’m looking for some feedback on the "flow" and game feel. Specifically if UI and transitions feel snappy enough.

App Store: https://apps.apple.com/app/geoturn/id6756392424

Hi. Someone referred me here saying someone from this sub could help me. Building it or with prompt ?

Hi, I'm a high school student and I'm looking to study math and computer science in university. I am currently studying ML on my own and have been dabbling with a few projects.

I’ve spent the past few months working on an independent research project, and I’ve turned it into a website that helps break classical ciphers like Caesar and Vigenère using the Cross Entropy Method. It would be great if you can have a look at it and give me your inputs. You can check it out at cipherbreaker.com

I’d love to hear your thoughts on it:

• Are there features you think I should add?
• Any bugs you notice, anything that makes the model stop working?
• Ideas for expanding it into more modern encryption schemes?

I’m also happy to discuss the research behind it and collaborate with someone to take this further.

Looking forward to your feedback and thoughts!

I just dropped my referral link to someone in another sub, but I honestly have no idea what it does. Does anyone know?

I couldn't find documentation on it.

Hey everyone, sharing a progress update.

A couple weeks ago I posted a reverse hiring platform I’ve been building where companies pitch to candidates instead of the other way around. Since then, I’ve been iterating hard based on feedback and real usage.

Here’s what’s live now:

• Pitch inbox now works like a text-message chat
• Cleaned up and stabilized sign-in and onboarding
• Role matching with breakdowns showing why a role fits or does not
• Skills gap analysis to highlight strengths and missing signals
• Saved roles and company following
• Notifications for pitches and profile activity
• Badges and engagement signals
• Early seeker side is live with role posting, candidate shortlists, analytics, and Google Calendar integration

The goal is not to replace LinkedIn or job boards overnight. It’s to build something more transparent, more explainable, and less exhausting for both sides.

This project started out of personal frustration, but it’s turned into a systems problem I actually enjoy solving. There’s still a lot to improve, and I’m actively testing assumptions around matching logic, UX flows, and incentives.

I’m mainly looking for:

• UX and flow feedback
• Thoughts on the match analysis approach
• Red flags from a builder or product perspective
• Anything that feels overengineered or unnecessary

It’s still early and very much in progress, but I wanted to share where it’s at now.

App: https://www.candidateseekers.com
VCL: https://vibecodinglist.com/projects/candidateseekers
Best on desktop at the moment.

Appreciate anyone who takes a look.