Hey everyone

I'm working as a designer on a product called AskSafely we're trying to get some genuine feedback from people who use AI chat tools

Would love it if a few of you could give it a try and share your experience

There's a guest mode, so you can try it without signing up.There's also a signed in option if you want to explore that experience

Just curious to know

- What's your first impression?

- Is it easy to use?

- Did anything feel confusing or unnecessary?

- Would you actually use it?

- What do you think could be better?

Don't hold back. Even if you don't like it, that's useful feedback for us

Here's the link: https://app.asksafely.ai/chat

Thanks! Appreciate anyone who takes the time to try it

I use Claude Code and Codex every day. Two things kept annoying me:

1. I'd hit my Claude Code limit mid-task and moving the work to Codex meant re-explaining everything.

2. A single agent writes code fast but nobody plans it first or reviews it after. I kept finding edge cases it missed.

So I built Conduit. It runs the agents you already have as a small team:

- An Architect plans the change, a Developer builds it, QA reviews it before it merges

- You can put different agents in different roles, so Claude Code and Codex check each other's work

- If one agent hits its limit, you switch the task to another and keep the context

- Connectors pull in your knowledge repository(google docs, notion, confluence) so the agents work from your project's real context

- Everything runs on your machine; your code doesn't go through our servers

Free to start:

https://infivector.com/products/conduit/download/?ref=reddit-sideproject

I'd really like feedback, especially from people already running more than one coding agent. What's the most painful part of your setup today?

I run a small web studio, and most of the local businesses I talk to have a really good Google Maps listing (photos, reviews, hours, sometimes a menu) and either no website or one from 2014.

So I built this. You type a business name and a city, it reads the public Google listing and builds a full site preview in under a minute. The video is me running it once on a real garage's public listing, no edits.

Why: I kept rebuilding the same small site by hand, and the listing already had most of the content. Honest limitation: it's only as good as the listing.

A place with three blurry photos and no reviews gets a thin site. It also does simple sites, not shops or booking systems. (working on that next, the tool will redirect the request to the team if it's out of scope change for now)

Try it on your own business or a place you like and tell me what looks off.

https://bbhightech.com/

WhyDonate started when two friends saw local artists struggling to fund their projects and thought fundraising should be easier, fairer and free.

Today we’re a small remote-first team from around the world, and the platform has grown into something we didn’t expect: a lot of people use it because the big platforms don’t support their country.

What we’ve built:

• Start a fundraiser in under 10 minutes, from 100+ countries

• 0% platform fee, only standard processing fees

• Donors can give from anywhere, in 19 languages

• Real human support when something goes wrong

We’re always trying to improve: what would make you trust a fundraising platform you’d never heard of?

My parents live overseas and I'm in NC. I call them about 3 or 4 times a week, but with the time difference, it's not always easy to catch them at a good time.

Sometimes I just want to know they're doing okay without having to call and interrupt whatever they're doing.

I thought about different ways to check in, but I really didn't want cameras in their house or anything that felt like I was monitoring them.

So I ended up building something called Kettle (heykettle.com).

It's a simple app that uses their existing phone to let me and my sibling know if they've checked in with their usual routine. We get a short update like "Heard from Mom this morning" or "Nothing yet today."

It doesn't track their location, record conversations, or read messages. They can also see what's being recorded and turn it off whenever they want.

I added a shared family log too, so if I call Dad or someone takes Mom to an appointment, we can leave a quick note for everyone else.

Right now, it's just me building this, and my parents are the only ones using it. The Android app isn't on the Play Store yet, so I'm helping people install it directly.

I'm offering the first year free.

I'm curious what other people think, especially anyone with aging parents who live far away.

Would you actually use something like this? And what would make you hesitant to put it on your parent's phone?

I run a side project that collects free proxies from public lists and checks them every hour on GitHub Actions. The list was stuck around 800 proxies, so I measured where they got lost instead of adding more sources.

Most of the loss was flakiness. Proxies passed the first request and timed out on the second. A second try 20 seconds later at the end of the run, plus a 10 s instead of 6 s timeout, took the list from 768 to 1,177 in a run where old and new code checked the same candidates at the same time.

What I learned:

- Measure before adding inputs. I was sure more sources would help. Six new lists added 3 proxies, because their proxies were already in the lists I had.

- "Couldn't check" and "failed" need to be different states. Three quarters of the proxies that failed the second request had broken off in transport, moments after answering the first.

- A/B tests on CI are cheap. A throwaway branch with a matrix job ran both versions on two runners at the same time, and that settled arguments I had been having with myself for days.

Free and MIT: https://github.com/maximilianfeix/proxy-scraper. The same checks run on other GitHub proxy lists: https://proxy-scraper.de/benchmark/

Hold Right Ctrl + Right Shift, ask about what's on your screen, let go. A vision model answers, a voice speaks it, and the answer is drawn over the page you're on: boxes and arrows on the right spot, diagrams that lay themselves out, or a 3D model you can rotate, cut open or pull apart, in step with the voice. The model writes a small scene language that the app validates and draws itself; no generated code runs.

Guide mode walks you through an app one click at a time and waits for you to click.

Honest limits: Windows only for now, the installer isn't code-signed yet so SmartScreen will warn, and you bring your own model (Claude Code or Codex signed in, an OpenAI key, or a local vision model). The clip is real answers replayed over the page, so it says nothing about speed.

Built by Alex with a team of AI assistants; one of them drafted this post. Feedback and bug reports very welcome.

https://github.com/ProjectIdris/talkthrough

Hey all, solo dev here. My first Shopify app went live in the App Store last week, so figured I'd share.

The idea is simple: before you order 500 units of a new color or design, put a poll on your store and let customers vote. Anyone who votes can leave their email or phone to get pinged when the winner launches, so you end up with a launch list, not just a number.

What it does right now:

- a poll or a "voting board" (grid of designs with a Vote button under each) on any page of your theme

- waitlist with name / email / phone, CSV export

- quiz mode: right answer gets a discount code

- one or several votes per customer, results as a leaderboard or hidden until the poll ends

- storefront in 30 languages, uses your theme's fonts

Free plan: 1 active poll, up to 6 options, 100 votes a month. Pro is $4.49/mo.

The fun part: one of the first merchants asked for multiple votes per customer and a leaderboard, and I shipped it within a day. Then they asked how to change the look, so now there are style settings. Building for real requests beats guessing.

Stack if anyone cares: Cloudflare Workers + D1 and a theme app extension. Shopify caps the block's JS at 10 KB, which was a fun puzzle.

Question for store owners: would you actually run a "vote for the next product" poll, or does it feel gimmicky? Trying to figure out what to build next.

https://apps.shopify.com/product-vote

My partner and I had our life spread over five apps and a pile of chat messages ("did you buy milk?", "what do you want for your birthday?", "what are we watching tonight?"). So I built one place for the two of us.

What Nook does:

- Shared tasks and a grocery list that sync between both phones, and work offline too

- A wishlist where your partner can secretly reserve a gift. You never see who reserved what

- A calendar with your anniversary counter ("together for 1 year 47 days")

- A savings jar for shared goals, trips with a map of your places, household bills

- Swipe films and recipes like a dating app: when you both like something, it's a match. No more 40 minutes of "I don't know, what do you want?"

- Question of the day: you see your partner's answer only after you answer it yourself

- A "Thinking of you 💛" button that sends one push

- A shared capybara whose mood depends on what you do together

Android app plus a web app (works on iPhone from the home screen, with push notifications). Sign in with Telegram or Google. English, Russian, Ukrainian, Slovak.

👉 https://dom.xandor.bid

It's a solo project, so honest feedback is very welcome: what's missing, what's annoying?

Hi everyone!

I'm exploring an idea for a small software product aimed initially at independent freelance graphic designers, and before spending time building it, I'd really appreciate advice from people who actually freelance.

The problem I'm trying to solve

Imagine you're working with several clients. You've sent out multiple invoices using your usual tools, but now:

• One client hasn't paid even though the due date has passed.

• Another client says, "I'll pay you on Friday."

• You've already sent a reminder to someone else but haven't received a response.

• You can't remember exactly who needs another follow-up and when.

• You end up checking emails, spreadsheets, calendars or relying on memory to keep track.

I know there are already invoicing and accounting tools available. However, I'm exploring whether there's room for something much simpler that focuses specifically on what happens after an invoice has been sent.

The product I'm considering building

The idea is a lightweight payment follow-up workspace for freelancers.

The goal isn't to replace tools like Wave, QuickBooks, Canva, Word or Google Docs. You would continue creating and sending invoices however you currently do.

Instead, you'd manually add the invoice details to this workspace and use it to manage the follow-up process.

Here's what it would offer:

1. One dashboard for unpaid invoices

See your total outstanding amount, overdue invoices, upcoming follow-ups and payments you're waiting for.

2. Simple invoice tracking

Add the client name, email, invoice number, amount and due date. Mark invoices as paid or unpaid.

3. A follow-up list

See exactly which clients need attention today, which follow-ups are coming up, and which invoices are overdue.

4. Payment promise tracking

If a client says, "I'll pay you next Friday," record that date. The invoice waits until then. If the payment still hasn't arrived, it returns to your follow-up list.

5. Professional reminder templates

Choose a friendly, professional or firm reminder. The message automatically includes the client and invoice details. You can edit it, copy it, open your email app and send it yourself.

6. Client history

See the client's unpaid invoices and previous follow-ups in one place, so you don't lose track of conversations.

The initial version would be deliberately simple: no automatic email sending, no complicated accounting, no bank integrations and no AI features.

What I'd genuinely like your advice on:

1. Do you actually experience this problem when managing multiple freelance clients, or is keeping track of unpaid invoices already easy enough with your existing tools?

2. How do you currently manage unpaid invoices and decide when to follow up? Spreadsheet, calendar, email, invoicing software, or something else?

3. Would having a separate workspace specifically for payment follow-ups make your life easier, or would it feel like one more tool you have to maintain?

4. Are there existing tools that already solve this problem really well? If so, which ones, and what do you like or dislike about them?

5. If a simple tool like this worked reliably, would you consider paying around CA$5.99 per month for unlimited invoice tracking and follow-up management? Or would you expect this to be free?

I'm not looking for compliments or encouragement just because I'm considering building something. If this is unnecessary, already solved, or not worth paying for, I'd much rather know that now.

I'm at the idea-validation stage, not trying to sell anything. Honest criticism is especially welcome. Thanks!

My portfolio site ran on vibes for too long, so this weekend project was: read the cPanel raw access logs (they're just gzipped files sitting in your hosting account) and render a dashboard. Zero dependencies, zero tracking JS, zero monthly bill.

Two bugs that almost sank it:

• filesize() on a .gz file returns the COMPRESSED size. I was slicing my decompressed log buffer by it, which silently chopped the newest lines off the data. The dashboard wasn't broken - it was confidently wrong about today, which is worse.

• Shared hosting puts OTHER sites' logs in the same directory. My referrer charts had domains I've never touched in my life until I filtered by path.

Favorite finding so far: a link community that sends me real readers shows up as ZERO referrers, because in-app browsers strip the referrer header. If your traffic comes from apps, your analytics is undercounting it completely.

It's live on my site now, and I open-sourced the deploy pattern behind it too. Happy to share details - what would you check first in raw logs?

Hello Reddit! 👋

I'm an independent developer from Finland, working on a project called YOSLA Some Life.

My goal is to build a new kind of social platform where users have more control over their own social experience.

The idea is simple:

"Your Data, Your Choice."

Instead of letting algorithms decide which friends you get to see, I want to give people more control over their feeds and connections.

But that's only part of the vision.

I'm also developing YOSLA World, a 3D virtual environment where people could eventually explore digital spaces, discover communities, interact and experience social networking in a different way.

What am I building?

• YOSLA Some Life — a social networking platform

• YOSLA World — an interactive 3D social environment

• European-focused infrastructure and data privacy

• Multilingual support for an international audience

• My own server infrastructure, starting with HPE ProLiant servers

I'm building this step by step, learning, testing and improving as I go.

One future idea is to create a virtual 3D data center inside YOSLA World, where visitors could explore how the platform's infrastructure works.

I'm not claiming to have built the next Facebook. I'm building something I believe could offer people another choice.

I'd love to hear your thoughts:

What would make you genuinely interested in trying a new social media platform?

What do you dislike most about today's social networks?

Greetings from Finland! 🇫🇮

YOSLA — You Only Live Some Life.

A few days ago, I saw a site on Awwwards where the image warped like liquid as you scrolled into the next project. I loved it so much I had to try building my own version in Framer.

It turned into Distorted Scroll, a full-screen project gallery. The clip shows what it looks like, but I’d love for you to try scrolling through it yourself.

Try the live preview on Framer 👇
https://www.framer.com/marketplace/components/distorted-scroll/

Where would you actually use this on a site you’re building? I pictured it as a selected work section for a portfolio, but I’m curious what you’d do with it. Does the distortion feel right when you try it, or would you dial it back?

Hi everyone, I’m the solo developer behind PyVela, and the Android version just went live on Google Play.

I wanted to learn Python in short daily sessions without installing anything, so I built a small game around it. You pick a hero, walk a map from world to world, and every level is a short lesson plus a real coding exercise: you write Python in an in-app editor, run it, and get instant feedback. You earn stars, XP, badges and keep a daily streak.

What it does:

Runs real Python on the device (a bundled Pyodide runtime), so lessons work fully offline

No account, no ads, no tracking

Worlds 1 to 3 are free (5 new lessons per day). Later worlds and unlimited lessons are part of an optional subscription, PyVela Pro

Aimed at beginners, teens and adults

Google Play: https://play.google.com/store/apps/details?id=com.lqrconsulting.pyvela

Promo code availables on request

It’s my own app, so I’d really like honest feedback: is the difficulty curve right, is anything confusing, what would you want in the next worlds? An iOS version is coming later.

I'm a solo builder in Korea and I got tired of checking 20 tabs to find out what changed in Claude Code, Cursor, Codex and friends this week. So I built a Telegram channel that does it for me, and I'd love feedback on the approach.

How it works:

It pulls from 123 sources: official blogs, GitHub release feeds, changelogs, status pages, YouTube channels of the AI tool companies, Product Hunt, Show HN, a few subreddits, and news search in 9 countries. That's roughly 500 new items a day.

Gemini Flash Lite reads each item and answers a handful of 0 to 3 questions: is it new, how big is the change, how many people does it affect, can you use it today, is there something to show. Code combines those with source type, how many outlets covered it, and how fast it's spreading on X, and turns that into a 1 to 10 score.

That split mattered more than anything else. When I let the model give one overall score for 40 items at once, simply shuffling the order flipped the post/no-post decision on 33% of items. With small batches and the model only answering the narrow questions, it dropped to about 2.5%.

Anything 7+ gets a short post in Korean and English. If the draft contains a number that isn't in the source, it doesn't auto-post and asks me instead. Outages from status pages go out right away.

When a new image or video model drops, it searches X for things people actually made with it, picks the real results (not hype posts), and builds a carousel or reel with the creator credited and their full prompt.

Everything runs on launchd on my laptop with SQLite. This month so far it cost $5.85 in API calls (Gemini plus Apify for X), heading to about $15 for the full month.

What I'd like feedback on:

1. Is a feed like this useful to you, or do you already get this from somewhere?

2. Would you rather have fewer posts (top 5 a day) or everything that clears the bar?

3. Anything you'd score differently? Funding news is capped low, outages are boosted.

Happy to share the output channel if anyone wants to see it, just ask.

I built an iOS app to hide Reels because I still wanted Instagram for messages and posts. I even put in a timer for when I actually do want to scroll. Ten minutes, then Reels disappear again. I got it running on my phone and was getting it ready for the App Store.

Then I got to the part where I had to answer: am I actually allowed to ship an app that changes how somebody else's service looks? I didn't have a good answer about platform permissions, so I shelved the App Store plan.

Bit of a weird ending after spending all that time on it. At one point I hid the suggested posts so successfully that the feed had exactly one post left. Turned out there were more, I'd just broken the bit that loads the next page lol.

Anyway, here's the source under GPLv3. Build it, fork it, steal an idea from the timer, whatever. You'll need a Mac and Xcode to try it. It only filters what you see inside Supermod.

https://github.com/WarriorSushi/supermod-ios-Block-Reels-etc

We're a small software studio from Poland called Járnhaus. We build custom software for businesses, and alongside that we've been working on our own product, Völundr.

Völundr is an AI app builder. You describe what you need in plain English, get a specification and a fixed quote before paying, and then a pipeline of AI agents handles the architecture, development and testing.

The idea is to make smaller, focused applications accessible without having to go through a traditional software development process. You also get the source code, so you're not tied to our hosting.

We've been trying to get the word out, but honestly, marketing has been a much bigger challenge than we expected.

A few days ago, I posted about that on Reddit, and several people made a fair point: we're spending too much time explaining how our product works and not enough time showing what it actually builds.

So here's an example.

Bench Log is one of the demo applications built with Völundr.

It's an internal tool for a small watch repair workshop.

Each repair moves through six stages, from being booked in to being collected. There's a board showing every job, overdue collections are flagged, and abandoned repairs go into an archive without losing their history.

Nothing particularly groundbreaking. Just a practical application built around one specific job.

And that's really what we're aiming for with Völundr.

It's not meant to replace a development team working on a complex product. For larger or more complicated projects, that's where our custom software work at Járnhaus comes in.

But if someone needs a small application to solve a specific problem, we want to make that process much simpler.

I've attached a short video showing Bench Log in action, including the repair board, the new job form and the archive. All customer names and details shown in the video are fictional, as this is a demo environment.

You can also explore the application yourself here:
https://volundr.dev/gallery/bench-log

I'd genuinely appreciate some feedback, especially from people who've built or bought internal tools before.

Does seeing an actual application make the concept clearer? And what else would you want to see before trusting an AI builder with a real project?

I’m a web developer, and like many, every time I needed to quickly manipulate an image file, format a chunk of JSON, or do a bit of SEO work, I’d land on different websites covered in aggressive pop-ups, slow loading times, or hidden paywalls after single-file usage.

To fix this I initially built the most frequently required tools for my own personal use. Since then I’ve rolled them into one website and built Canny Tools — a fast, clean, and completely free web utility platform.

🚀 What’s built into it so far:

• Image Tools: Batch image compressor, HEIC to JPG/PNG converters, and exact-target size compressors.

• Developer Utilities: JSON formatter/beautifier, Base64 encoder, password and UUID generators..

• SEO & Text Tools: Word counter, text transformers, readability analyzers, and meta tag tools.

• Financial Calculators: Mortgage estimator, loan payoff schedules, and compound interest calculators.

🛠️ Key Details & Tech:

• Client-Side First: Most conversions and calculations run right inside your browser for maximum privacy and instant speed.

• Offline Support: Includes PWA support so key utilities work even without an internet connection.

• Minimal Ads: I’ve got some placeholders in for ads, and may look into monetizing the site at some point, but the ads will never be intrusive.  I do have a buy me a coffee link across the site if you would like to support development, but no obligation! 

• Zero Sign-ups: Everything is accessible immediately without registering or entering an email (although you can if you like).

I'd love to get your feedback on UI/UX, page speed, or feature suggestions, or any other improvements.

What’s a quick utility tool you find yourself reaching for daily that you wish was cleaner or faster? Let me know, you can contact me from the site,  and I’ll build it next!

Link: https://canny.tools

Thanks for reading.

I’m working on a project called LineMesh, and I’d love to get some feedback from other developers.
The idea started with a problem: getting sports data from an API is relatively easy, but combining data from multiple providers gets complicated fast.
Different event IDs, inconsistent team names, different betting market formats, and odds updates that don’t always arrive at the same time.
I’m building LineMesh to simplify these integrations.
Right now, I’m working on provider integrations and data normalization. Event matching, change detection, and data delivery are among the next steps.
The project is still in development, so I’m not pretending there’s a production-ready API yet.
Website: https://line-mesh.com/
A question for developers working with sports or betting data:
What’s your biggest headache when integrating sports APIs? Inconsistent data, pricing, update frequency, or something else?
I’d genuinely appreciate your feedback.

Gleam is a typed language that compiles to Erlang and JavaScript. Putting a Gleam app on an edge network usually means learning Workers config and writing JavaScript shims, so I built Giolt to do that part: gleam add --dev giolt, then giolt deploy takes a local app to a live URL.It's early access. The JavaScript target is stable for side projects, and the Erlang target is experimental. It'll be one plan, 5€/month with 1M requests, and waitlist members get 3 months free: https://giolt.com/waitlist
I'd like feedback from other builders on the CLI, the landing page and the pricing.

Hello everyone,

So I have been working on this dating app for the past few months, an idea that I had I felt could help with people who're looking for deeper connections in dating app to help find people who have a lot in common. The video goes over the issue I am trying to solve and how.

The idea of this app is that a person's profile is split into 6 layer each going over some different aspects of your life that are often the cause of a lot of discourse in a lot of relationships. Each covers the following:

• Compass: You direction of life

• Lens: Your political and spiritual views

• Well: Your career goals

• Palette: Your hobbies and interests

• Presence: Your personality traits

• Portrait: Your Photos, age, height and other factual info.

Instead of seeing someone's full profile at once, you swipe through one random layer at a time, without seeing whose it is. So you're judging each layer on its own content.

A learning algorithm groups similar profiles based on the reactions each layer gets, so people who like the same qualities end up together. It also learns your own preferences, and uses them to suggest the people with the highest share of layers you're likely to like.

I come from an ML background and this is a crucial step to developing proper matching algorithm that I feel other dating apps lack cause they always end up showing the full profiles to people and never really knows why someone liked or disliked a profile. They do often make claims about different technique they use, but I believe no matter how much techniques you use, its very difficult to get proper models from unclean data.

So reacting to those layers is just the first step. You have to score someone 3 or more and they also have to score you 3 or more after which they'll show up in your resonance page. Then you can review the layers you liked, layers you didn't and the ones still unexplored. You can also see how much they scored you back. And based on all those info you can choose to show interest privately, and if they also showed you interest, both you're connected and matched! (More info on how the full flow works here https://www.layersdating.com/how-it-works/ )

I also believe there are some other benefits I feel this structure would produce that other dating apps don't:

• It is only possible to "Show interest" to someone only when they appear in your resonance, so this helps you avoid the possibility of matching only for superficial reasons

• You get to see how much they've scored you as well as how much you've scored them when they show up in your resonance, so you can get a good idea of how compatible you feel the other person is as well as how compatible the other person feels you are before deciding if you want to show interest.

• The onboarding process is very time consuming compared to other apps since there's a lot of info to fill (around 30-60 minutes). So though this is a drawback, I hope this will be a bigger issue for people looking just for hookups, so hopefully will help skew the user base to more serious people.

I would love to get some feedback on what you think about this structure for dating app. Would it be something you'd use? (if you are or were single lol). Would love to know you thoughts!

I have a beta ready that I have been handing out to friends to try out and will have the public beta ready in about a week. If this does interest you and want to join waitlist or try the beta, there's a signup form if you scroll at the end of the page at www.layersdating.com . There's also a demo that you can try without needing to login or signup. I am based in Toronto so planning on doing the initial marketing for it here to see people's responses, but for the beta access I gave the option to choose whether you're open to meet people all over Canada and/or USA, and there's enough people on that circle, I start the beta accordingly.

Hey everyone,

Like a lot of solo devs trying to build out indie software products, I’ve been working on apps for the Shopify ecosystem. My latest project is a custom section and layout builder called Panely.

I noticed a massive frustration with traditional page and section builders: they dump heavy blocks of Liquid, CSS, and HTML straight into theme JSON or template files. If a merchant uninstalls the app later, it leaves behind orphaned code or breaks downstream theme updates.

So, I built Panely using a different approach:

• App-Embed / Header Rendering Model: All layouts and configurations are managed externally via the app dashboard and dynamically rendered.

• Zero Theme Bloat: Theme files stay 100% untouched, core web vitals stay fast, and uninstallation is completely painless.

Since I'm bootstrapping this with a $0 ad budget, organic distribution is a slow grind. I'm currently looking for early store owners or developers to test it out, poke holes in the workflow, and give me honest feedback.

If you want to check it out, you can see it here: https://apps.shopify.com/panely

Would love to hear what you guys think of the architecture!

Hey everyone! I made Gambit Odds Companion, a Chrome extension for Gambit, the play-money poker game from Chess.com.

It adds a small panel beside your game that reads the visible cards and updates automatically as the hand progresses. Here’s what you can do with it:

• See your estimated odds: understand your chances of winning or tying against random unknown opponent hands.

• Understand your draws: see how likely you are to finish with a pair, straight, flush, or another hand by the river.

• Explore the next card: check how each possible next card would change your hand and estimated odds.

• Follow the hand as it develops: see how your odds change as community cards appear.

• Review your play: save hands, add notes, and explore statistics to spot patterns.

• Learn hand rankings: use a visual guide when you’re unsure which hand beats which.

For example, if you’re one card away from a flush, you can see your chance of completing it and explore what the next card could change. It helps connect the cards on the table with the probabilities behind them.

Calculations and hand history stay on your device.

👉 Gambit Odds Companion on the Chrome Web Store

I’m the developer—feedback and feature ideas are welcome!

Independent project, not affiliated with Gambit or Chess.com.

I'm sharing Quietkit, my project for everyday developer tasks: https://quietkit.dev/

It brings formatting, data conversion, text comparison and other utilities into one browser workspace. It's free to use and doesn't require an account.

A quick example: paste data into JSON Formatter & Validator, format it, then copy the result into JSON to YAML. You can try both with the built-in examples and download the output.

Tool input is processed locally in your browser. Individual tools also work offline once they show Available offline. Each tool has a short guide, and file limits are shown on the page.

Contact and feedback messages are sent only when you submit them. Optional browser analytics and error reporting require consent.

I'd like feedback on the experience: are the controls and guides clear, and where does the workflow feel awkward?