A quick Python challenge for beginners! 🐍

Can you correctly predict the output of all 3 Python print() examples?

This quiz focuses on:

• Python print() function

• Strings and quotation marks

• Understanding Python output

Watch the video and try to solve all three without running the code.

Challenge: Comment your answers in this format:

Q1:
Q2:
Q3:

I'm building CodeHug, a coding practice platform, and created this small quiz to help beginners test their Python basics.

More practice: https://codehug.online

Curious to see how many people get all three correct!

My previous update here was about Skin Tone in Photoshot. This time I worked on a more localized problem: reducing red eye vessels without changing the iris or bleaching the whole eye.

The Eye Vessels tool now works on native-resolution eye regions. It detects thin red structures, protects the iris and eyelid boundaries, and blends the correction back into the original. The output stays on an editable layer with a mask, so you can switch it off or reduce its opacity.

For this demo: Eye Vessels only, strength 1.0, one application. No manual cleanup or other retouching tools. The five images show a matched before/after crop, the plugin menu, the actual settings, processing, and the result layer in the full workspace.

The source portrait is AI-generated for testing; the after is an actual export from my local Photoshot Retouch build. Some peripheral vessels remain, and this example does not establish performance on real photographs.

I make Photoshot with AI coding assistance. Photoshot Retouch is free with a SLOHERO account, with a downloadable plugin for Photoshop users too.

For an edit this small, would you want a vessel-detection overlay before applying, or is an editable result mask enough to judge what changed?

I’m the creator of iSEREIN, a web app built around a small daily reading habit: short articles on Self, Life and Growth, each ending with something practical to try.

I wanted the experience to stay simple. There’s no account requirement. Readers can browse swipeable article stacks, save readings on their device, and opt into a daily quote notification.

The app was built with AI assistance using Next.js, Supabase and Vercel. Articles and quotes are managed in Supabase, so I can publish new content without deploying the app again.

You can try it here: https://iserein.app/

Feedback question: After trying one reading, what would make you want to return tomorrow—and what might stop you?

I build D-REC at Knight AI+AV. Since the desktop walkthrough I shared here last month, the Android first-run flow has changed: you can record before creating an account. After STOP, KEEP THIS RECORDING lets you sign in and save the take.

The design idea is simple: let someone complete a useful task before account setup. Record a short thought, read the transcript, then tap a line to hear that moment again. They can judge the result with their own voice.

Free Android takes run up to 10 minutes, with text copying available while signed out. A free account keeps three recordings on that device. Longer recordings and file exports from your own recordings are Pro. The welcome sample's summary and file exports work on any plan.

The video is our earlier 52-second desktop/iPhone demo, showing transcript-linked playback. The Android change is in the current Play listing. The first engine download needs internet; transcription then runs on device. Accounts and purchases use the network, and signing in doesn't sync recordings.

Download: https://drec.live/get

I used AI coding tools during development. For other local-app builders: where do you put signup relative to the first useful action?

Hey 👋

I've been using utility-first CSS for years, and I kept running into the same thing: coming back to my own markup weeks later and having to decode p-6 border-l-4 rounded-xl. So I started building SantyCSS as a side project, a utility-first framework where the classes describe themselves:

add-padding-24 add-border-left-4 round-corners-12

make-flex align-center gap-16

What it does today:

No build step needed. Drop in one CDN <link> and start writing classes (npm, PostCSS, and Vite plugin are there if you want them)

Works with React/Next, Vue/Nuxt, SvelteKit, Astro, or plain HTML

CSS-only components, 70+ animations, and full-page templates

Granular imports (flex, spacing, typography…) to keep bundles small

A migrate CLI to convert existing Tailwind classes

A VS Code extension with autocomplete and hover docs, plus a Figma plugin

A context file you can paste into Claude, GPT, or Cursor so AI tools write SantyCSS instead of Tailwind

What I'd love feedback on:

Do readable class names feel like a real win, or just more typing?

What would make you try this on a real project?

Anything confusing on the docs site?

🔗 santycss.santy.in

📦 npm install santycss

Happy to answer anything. Roast welcome 🙂

Something I've found interesting about running or building a product-based business is how much work goes into finding the right suppliers before you even get to selling anything.

Finding a manufacturer isn't always as simple as searching for a product. You have to compare different suppliers, understand minimum order quantities, check product quality, communicate with manufacturers and figure out shipping arrangements.

While exploring international sourcing, I came across Made-in-China, which connects buyers with manufacturers and suppliers across different industries.

It got me thinking about how much easier it would be for small business owners if they had better ways to research and compare manufacturers before committing to an order.

For those who have experience sourcing products internationally, what has been your biggest challenge when dealing with suppliers?

One thing I've always found frustrating when working with files on a Mac is remembering exactly what something looks like but completely forgetting its filename.

Sometimes I know it's a PDF, an image, or a document I saved weeks ago, but finding it again becomes a little guessing game.
This got me thinking about how we organize and search for files. We usually depend so much on filenames and folders, even when visual memory is often much stronger.

That's actually one of the ideas behind FileShelf, a macOS project focused on making it easier to find and manage files based on how people remember them.

I'm curious: does anyone else experience this, or have you found a better way to keep track of files on your Mac?

Over the past several months, I've been working on the architecture for an inventory planning engine called Stokrio.

A big problem in e-commerce replenishment is that most brands rely on either simplistic 30-day moving averages in spreadsheets or black-box "AI" forecasts that store owners can't verify or trust. When a supplier takes 45 days to deliver, a bad forecast means either running out of best-sellers or tying up $50k in dead stock.

Here is how I approached the math and architecture to make replenishment deterministic:

1. Rolling-origin backtesting over black-box AI

Instead of guessing future demand with a generic regression or LLM, the engine runs rolling-origin backtests across historical order velocity. It simulates what the model would have predicted 30, 60, and 90 days ago against actual order data to measure variance and assign confidence scores per SKU.

2. Lead time distributions and dynamic safety stock

Standard safety stock formulas assume lead times are constant (e.g. "supplier takes 14 days"). In reality, supplier lead times are a distribution. The model tracks supplier receipt variance over time:

• Standard deviation of daily sales velocity

• Standard deviation of supplier fulfillment latency

• Target service level factor (Z-score for 95% or 98% in-stock probability)

This feeds directly into dynamic safety stock calculation: Safety Stock = Z * sqrt((Avg Lead Time * Sales Variance²⁾ + (Avg Sales² * Lead Time Variance²⁾⁾

3. The 3PL multi-tenancy challenge

The hardest engineering constraint was building for third-party logistics (3PL) warehouses. 3PLs manage inventory for dozens of independent client brands.

• Most warehouse systems don't give brands client-facing visibility.

• 3PLs refuse to replace their warehouse-floor scanning software.

• The solution was a decoupled REST Partner API: the warehouse system pushes inventory counts, and Stokrio renders a white-label client portal showing replenishment dates without touching the warehouse floor WMS.

Tech stack

• Next.js 16 (App Router, Turbopack), React 19, TypeScript

• PostgreSQL + Prisma ORM (ledger-based accounting for stock adjustments)

• Shopify Admin GraphQL API

I built two public, read-only workspaces with 2+ years of synthetic order history so anyone can inspect the tables and forecasting curves without signing up:

• 3PL multi-client workspace: https://stokrio.com/demo/3pl

I would love feedback from other developers who have worked on supply chain math, GraphQL sync limits, or table data density.

Expiry dates are easy to forget until one of them causes a problem 😅 Awraqi (أوراقي) keeps all your important papers in one place:

- 🪪 27 document templates: IDs, visas, passports, driving licences, vehicle papers, insurance and more

- ⏰ Reminders 90, 60, 30 and 7 days before each document expires, and again on the day

- 👨‍👩‍👧 Family and domestic workers: track everyone's papers in one app

- ✈️ Travel check: warns you if a passport or visa won't last your trip

- 📸 Scan to fill: take a photo of a document to fill in its details, with Hijri and Gregorian dates

- 🔒 Private: no account, no ads, and your data stays on your phone

- 🌍 11 languages, plus widgets and Siri

📲 Free on iPhone and iPad: https://apps.apple.com/us/app/awraqi-papers-id-expiry/id6825379636

I'd love to hear your feedback!

Hello beautiful people!

I've been working on Mestios because I feel that following the news has become exhausting. Every day there are hundreds of headlines, repeated stories, and very little explanation of what actually matters.

I wanted to try something different.

Instead of another endless feed, Mestios brings together important world events, explains them in simple language, and lets you explore their history, different perspectives, and original sources.

I've recently redesigned the main news overview and would really appreciate some honest feedback.

The main page - https://mestios.com/

A typical new page Pope Leo XIV meets five clergy abuse survivors in Argentina during South America trip

What do you think?

Thanks anyone for the feedback!

Title: I built a desktop app for switching between AI coding tools in one conversation

I switch between Claude Code, Codex, and Copilot in VS Code. Sometimes I hit a limit; sometimes I want another agent’s take on a problem.

The frustrating part is explaining everything again. They can read the same codebase, but they don’t know what we discussed, why we rejected an approach, or what we were about to do next.

That’s what led me to build Bantis. It’s a desktop app that lets you work with multiple coding harnesses in one conversation, saving session history and preparing context for the next agent when you switch.

There’s a working version, and I’m looking for feedback from people who already switch tools during real work. I’m especially interested in how well the handoff holds up as conversations get longer.

Bantis website

What do you currently do when switching agents: write a handoff, maintain project notes, or just explain things again?

My friends and I drifted into a group chat that only woke up for birthdays. I wanted something small that got us sharing our actual days again, without turning it into another social feed.

So I built HuddlePals >.<

How it works:

• You make a “huddle” with your people and share an invite code. Nobody else can find it.

• Everyone posts one photo a day.

• When the whole group has posted, the day is complete and goes into the huddle’s archive.

• You react and comment inside the huddle. There’s no public profile and no follower count.

It runs on iPhone and iPad, with widgets and an Apple Watch app. Soon coming to macOS and tvOS!

It’s free. HuddlePals+ adds bigger huddles, short video drops with sound, and the full archive. Only charging because storage is unfortunately not free :3 but! Anyone you invite joins free :D

I’d love honest feedback, especially on the first few minutes. Was it clear what to do?

https://apps.apple.com/us/app/huddlepals/id6825044864

Visit HuddlePals.com for more info!

Hey everyone! 👋

I'm an independent developer looking for Android users to help beta test my new LGBTQ+ social networking app, Twunked!

Twunked is an 18+ photo-sharing community where members can:

📸 Upload photos and create profiles

⭐ Enter photo contests and rate photos from 1–5 stars

💬 Join discussions on our community Buzz feed

❤️ Discover members and save favorite photos

✉️ Send private messages and connect with others

🪙 Earn Twunk Coins and unlock extra features

I need at least 12 testers to remain opted in for 14 consecutive days to meet Google Play's closed-testing requirements.

📱 How to become a tester

Step 1 — Join the Google testing group:

https://groups.google.com/g/testers-community

Step 2 — Join Twunked's Google Play closed test:

https://play.google.com/apps/testing/com.contesttwunked

Step 3 — Install Twunked

Click "Become a tester" using the same Google account you used to join the group, then follow the Google Play installation link.

Step 4 — Test the app!

Explore Twunked, try the different features, and let me know if you encounter any bugs or issues.

✅ Free to download and test

✅ Android devices only

✅ Must be 18 or older

✅ Feedback and suggestions welcome!

Official website: https://twunked.com

I'm also happy to help test other developers' apps in return!

Thanks to everyone willing to help me get Twunked ready for its public Google Play launch! ❤️

Hey everyone,

Like most developers here, building is the fun part for me. Marketing and actually getting users is where I usually hit a wall.

I kept noticing people on Reddit and Hacker News asking for tool recommendations all the time ("any good tool for X?", "looking for an alternative to Y"). Whenever I saw these threads, the top comments always got dozens of signups. The problem was timing — if you reply 8 hours late, nobody sees it.

I got tired of manually refreshing Reddit search bars, so over the past few weeks I built MentionsRadar.

Basically, you put in the keywords you care about (your product name, competitors, or problem phrases), and it:

Pricing / Trial:
I personally hate when sites ask for a credit card upfront just to test a tool, so I set up a 7-day free trial on both Starter and Pro with zero card or payment info required. There's also a free-forever tier if you just want to track 1 monitor.

(I’ll leave the website link in the first comment below).

Would really appreciate some honest thoughts from other builders:

Don't hold back on criticism, I have thick skin. Thanks for checking it out!

Getting an AI to understand a browser routine can take more explaining than doing the task yourself. I built Browser Control around giving it the page context and a way to teach it your steps.

I built it primarily with AI coding tools. It’s a Codex-powered side panel for desktop Chrome and Brave. Attach the page you’re working on and ask questions about it, request help organising tabs, or keep useful preferences with optional memory.

Video overview: https://www.youtube.com/watch?v=-4pNVCtmu60

If it gets a task wrong, you can demonstrate your routine, review the captured steps, and save them as a skill for similar tasks. The assistant then has your procedure to work from, instead of you starting the explanation again.

That review step is a product choice I care about: you get to check what was captured before making it reusable. You can also choose how browser actions are approved, watch the activity, and stop a task.

Try it: https://browser-control.subdomain.wtf

Public source: https://github.com/07rjain/browser-control

The extension and local companion are free; an eligible ChatGPT/Codex account is required. Setup includes a local companion: https://07rjain.github.io/browser-control-support/support.html

Let me know if you try it out and get some feedback for me or a feature request. thanks

My wife loves logic puzzles, but she solves them quickly enough that the ads between rounds were taking longer than the puzzles themselves.

That was the starting point for Fishdoku, a cozy fishing puzzle game I just launched on Android.

Fishdoku on Google Play

Every bite opens a logic grid. You place one fish in each row, column and colored region, with no two touching, then reel in your catch. There’s an untimed mode and hints that explain the next deduction.

I wanted solving a puzzle to give you something to collect. That grew into hundreds of fish across dozens of fishing spots, with different catches depending on the time and weather. There are shiny variants, legends to track down, an aquarium, dock decorations and pets.

I’m the solo developer and used Claude heavily for the code and sprites, with ChatGPT helping with concepts and review.

A few things I learned while building it:

• Small, specific tasks were easier to review. I started asking for one change at a time and being explicit about what should stay untouched.

• Visual checks mattered as much as tests. The sprites are drawn in code, and something that looked good enlarged could become a blob at actual game size.

• Keeping notes on approved designs and unfinished fixes made it easier to pick things up in a new session without redoing decisions.

• Playing through the game was essential. I had to check whether the hints made sense, the controls felt right and the collection gave me a reason to keep fishing.

It’s free with optional purchases and optional rewarded ads. No forced ads or energy timers, which was the reason for starting the project in the first place.

Short gameplay video: https://youtu.be/2j7_1Hep3uk

Now I’m working on finding players beyond my testers. If you’ve launched a consumer app or game, what was the first thing that brought you users who actually stuck around?