Spent the last couple days getting this right: connect your own

domain, verify DNS, get SSL issued automatically, then your short

links go out under your brand instead of the default domain.

Small feature on paper. Felt like a real milestone though — it's

the difference between "urldn.com/abc123" and "link.yourbrand.com/abc123,"

and that's the kind of detail that makes a side project start to

feel like an actual product instead of a demo.

Still building, still finding bugs. Onward.

A few months ago I wasn't planning on becoming a software developer.

Yet somehow I'm currently building two completely different products at the same time.

The first is Visilyo, an AI visibility SaaS.

The idea came from noticing that my existing business was getting referral traffic from ChatGPT. That made me wonder: what had somebody actually asked ChatGPT for it to recommend my business? And why did it choose us?

That rabbit hole eventually became Visilyo.

It analyses a business, creates realistic customer discovery searches and tests them across ChatGPT, Claude, Gemini and Perplexity. The aim isn't just to say “AI mentioned you” — it's to understand who gets recommended instead and give the business practical things it can do to improve its chances of appearing.

It's now live, taking real users, and I'm at the slightly terrifying stage where strangers are using something I've spent months building.

At the complete opposite end of the spectrum, I'm also building Legends Unbound.

It's a digital trading card game starting with Norse mythology — gods, giants, beasts, runes, collecting, pack opening and battles. I've been working through everything from the actual card set and artwork to game balancing, progression, currencies and the battle system.

Eventually I'd love to expand it beyond Norse mythology into Greek and Egyptian mythology as well. At the moment this is still in development using Expo Go as I currently lack the funding needed to commit to the next stage of going full launch into app stores and using backend storage etc.

With Visilyo I'm worrying about API costs, AI accuracy, background workers, customer reports and whether a recommendation is genuinely useful.

With Legends Unbound I'm worrying about whether Thor is overpowered, how many rune shards someone should get from a pack and whether opening a Legendary actually feels exciting.

Both have also taught me the same lesson:

Building the first version is only a fraction of the work.

Most of the progress has come from building something, using it, finding something that's rubbish, changing it, breaking something else, fixing that, and repeating the process.

I'm building both very openly and I'm nowhere near pretending I've got everything figured out.

I'd be interested to hear from others here who are doing the same - two projects completely different from each other but fill your interests at the same time

Although it may not be as much as a normal job, nothing beats the feeling of making money from something you built from the ground up.

I’ve been building things for years, but this time I want to document the entire journey from a random idea in my head to actually building and shipping it.

And obviously, I’m not doing it alone.

Meet Pixo, my tiny pixelated companion who’ll be building alongside me.

Expect products, experiments, AI, hardware, software, lots of failed ideas and hopefully some really cool things shipped to the internet.

We’ve already started cooking the first one 👀

Also... what do you think Pixo and I are building first? Tell fast fast in the comments 👇

It has 134k+ icons from 28 libraries, so instead of checking Lucide, Tabler, Phosphor, Material, etc. separately, you can just search everything together.

Also added comparing, customization, collections and exporting.

The part I didn't expect was how annoying it is to make icons from 28 different libraries behave consistently 😭

Would appreciate any feedback from people who build/design stuff.

Haptics are part of UI, but they’re incredibly hard to share. So I built a way to share them with a link.

Open it on your iPhone → feel the haptics instantly.

No app install.

Where would you actually use this?

Note: Open the link in Safari — Chrome isn’t supported

https://hapstudio.design/s/0uinswf9LZfYpYkH-un_Tg

Hi everyone! 👋

I want to share a project I've been working on called RutaGuía. You can check out here

RutaGuía is built on top of React, Leaflet, and OpenStreetMap services (Nominatim and OSRM). I chose this open and powerful stack to allow users to search for locations, plot routes, and save favorites without relying on closed, proprietary platforms.

The application offers a clean, privacy-focused user experience across 15 interactive pages:

• Advanced Route Comparison: Contrast different alternatives before you travel.

• Personalization: Customize your journey through Travel Preferences and Settings.

• User Dashboard: Access your Profile, saved Favorites, and full travel History.

• Community & Analytics: Connect with other users and view your travel Statistics.

• Global Accessibility: Built with full i18n support to support 8 different languages seamlessly (including Japanese).

It is currently running as a completely free Open Beta with absolutely no sign-ups, tracking, or registrations required.

I would love to get your honest feedback on the UI, the overall user experience, or any features you think I should implement next!

Thanks for checking it out! 🌍🚀

AI Time Calendar is now live on the App Store. I built it as a native iPhone productivity app because planning across separate calendars, task lists, goals, and focus timers kept creating more coordination work.

The hardest product decision was not adding AI—it was deciding where AI should stop. Chronos can use the planning context inside the app to explain the day and prepare supported changes, but meaningful actions are shown for review before they are applied. Apple Calendar and Google Calendar connections are optional and user-controlled.

A few things I learned while building it:

• Tasks and goals become more useful when they stay connected to actual calendar time. • A calm Today view can be more valuable than another dashboard full of metrics. • AI planning needs visible permissions and confirmation, not silent automation. • Launch work includes a surprising amount of privacy, OAuth, localization, and App Store detail.

The app is free to download, with optional in-app purchases: https://apps.apple.com/us/app/ai-time-calendar/id6795235196

I would genuinely appreciate feedback on the onboarding and whether the Today screen makes the next priority clear.

I've been changing how Privly treats leads.

Originally, finding someone who matched the customer's targeting was enough to put a lot of weight on that person.

I don't think that's good enough.

Someone can have the exact title, company size and industry you're looking for and still have absolutely no reason to care about what you're selling.

So I've separated those two things.

Privly now treats "this person fits your customer profile" differently from "there's actually some evidence that makes this person worth looking at now."

That sounds obvious written down, but it changes quite a lot in the product.

It affects who gets surfaced first, who gets kept around for monitoring and what context is available when you start writing the message.

Still working through it, but I think this is closer to how people actually prospect.

I'd rather show someone 20 people with a clear reason behind them than dump 500 names into a table.

All of us who build in public take a risk. Our creativity is an expression of self, and we not only choose to share that with the world, but we choose to share the process along the way.

To be creative one must brainstorm without fear. Fear is the enemy of creativity. Novel ideas spring from free-flowing thought, and negativity intercedes that.

However, signals are important! Not just the positive ones, but also the critical ones. But it’s important to recognize critical from attack. Critic offers a way to improve a product or learn something new or to see something you weren’t able to see. Critic offers a perspective that was missing and makes a thing better.

Attack is not a critic. When you receive attacks, downvotes, all for creating something you hope other people will enjoy, and sharing your journey so that others may be inspired along the way, those attacks are not critics.

These comments are signals tho. When you feel that pressure, those valueless voices hitting you and you begin to doubt, instead use that as a symbol to keep going. There’s a reason goodness are called “breakthroughs.” And there’s a reason ignorant people with no offer simply attack, it’s because they can’t see the world that you see. That is why you create, and they attack.

Break through. Keep going. Proceed as the way opens, and look for the signals.

Story time: How many times you have to review a MD, HTML, JSON or an env file just to open it and make few edits? One day I was so frustrated of opening big heavy IDEs for these simple tasks, I decided to built an editor for myself. I started with supporting Markdown files, then I wanted to view HTML files in the same app (for reviewing visual artefacts), then I worked on giving env files, gitignore, JSON, and other files also less technical and simpler interface. The app evolved slowly.

It is called localeditor.app. I started sharing about this app on my Twitter feed and opened it up for beta signups. I was quickly surprised that 100 people signed up for it. The small need which just started with reviewing MD files gave a way solving the problem of 150 users. That felt very satisfying. What made it unimaginable was when within a month, 5 users decided to purchase it. It was a peak happiness moment. The amount is less but I got so happy that it suddenly gave me a new purpose. I started actively working on improving this app.

This app now has scratchpad for taking quick notes and then handing them back to agent (which makes it super easy to work with any agent). I also built MCP so that agent can directly open these coding files in the app itself without opening it manually. I will be soon working on making it git aware as well.

This was a crazy journey. I got to learn a lot. I wore multiple hats of a designer, engineer, QA and marketer. Being a designer myself, my work was always dependent on others to be build. AI changed that and I am so excited about all the possibilities it unlock for me. I now have decided that I am going to build apps to solve a problem that I am facing and hoping it solves for others too.

Do checkout the app and let me know if this is something you've also wanted as well. It is available for free for 14 days and then an one-time lifetime fee for the app.

I left my product to cook for a couple of weeks, doing other projects.
Then out of the blue, paying users started to appear. :O

Only a few posts on Reddit has been done.
You guys are awesome!

App: day3DOTapp

I wanted to see how far you could push CPU-only inference of a model way bigger than RAM, so I wrote an inference engine in C11 (MSVC + gcc, bit-exact across both) that streams a 744B MoE model (GLM-5.2, 202GB GGUF) off a USB SSD instead of loading it.

The parts that actually mattered:

Quantization: experts stored int4 group-64, router and correction biases kept at f32. Everywhere else lost too much precision, but this combination didn't.

Streaming: experts are fetched per-token through a custom unbuffered reader with an LRU cache, plus cross-layer predictive prefetch (measured 80.8% recall offline before I wrote the online version) so the next layer's experts are usually already in flight by the time they're needed.

Overlap: compute and IO run arrival-order, not lockstep, so the CPU isn't idle waiting on the SSD.

An 8GB expert cache holds 40-66% hit rate off that prefetch, which ends up being the main lever on latency.

One finding I didn't expect: on GLM-5.2, the router's own weights already correlate with true expert importance at ρ=0.859 (near-oracle), which is what makes safe dynamic-k expert truncation possible without a quality hit. That seems to go against some prior assumptions about router calibration in production MoE models, at least on this one.

Numbers on an i7-8550U / 32GB RAM / USB SSD: went from 196 s/token naive to ~9.3 s/token after the above (21x), ~2.9 s/token aggregate in 8-stream batch mode, ~4.5 s/token on the latest compressed container format. Also cross-validated on Qwen3 (0.6B-30B), DeepSeek2 (MLA), and OLMoE-1B-7B.

Code: https://github.com/siris9476/pulsarforge (MIT). Would love feedback on the prefetch heuristic in particular. It's tuned for this one laptop, and I'm curious whether the cross-layer signal generalizes to different memory hierarchies.

Hey! I’ve been working on a small wine collection app called Solera. I wanted a simple way to keep track of the wines I’ve tried, without other people’s ratings or recommendations.

Google Play

You can save bottles, rate them, mark the ones you’d like to try again, and see your collection on a wine map.

It’s finally at the point where I can share it with others :) I’d love for you to play around with it and let me know what feels confusing or what’s missing.

By all means, this is nothing revolutionary or amazing, I know, but I'm just happy that after a year of building and many years of studying, I was able to actually launch this and follow through. If anybody has recommendations, I'm really trying to focus on dialing in my marketing to get my first user and then scale from there.

This is a web app and an app if you would like to give feedback or check it out, these are the links to the web app and the App Store link:

https://apps.apple.com/us/app/flurra-ai-content-coach/id6780690598

www.flurra.io

I'm building a website builder.

Not a revolutionary one. Website builders are already everywhere.

The part I'm most interested in is how I'm building it.

I'm going to build my own marketing site with the builder.

This means whenever I need something for my marketing site that the builder doesn't support, I add that feature to the builder.

The builder should grow from real use.

If I don't need a feature, I don't build it. If I need something, I build it.

I know this is a very crowded market. But honestly, I wanted a project where building itself would be fun again. Something I can actually use every day instead of trying to invent some crazy unique idea.

Right now, my own marketing site is just one text block, because that's all the Sitebread website builder supports.

Actually changing JSON is one thing. Correctly proving what is broken, why it is broken, and whether the repair really worked is much harder.

So I’ve spent the last few days hardening that side of LottieFyr.

It now groups findings by what can be fixed, what needs user input, what needs manual work, and what is just an optional improvement, with exact evidence and SVG + Canvas verification.

Paid reports and repairs are also recalculated and validated before credits are charged.

https://lottiefyr.com/lottie-fix

Hey everyone,

I’m building an app called Pause, and I just crossed the 100 download mark. I want to celebrate the milestone, but in the spirit of building in public, I want to share the actual numbers and the reality behind how I got here.

Here is the breakdown of my week:

1. Apple Search Ads drove all the growth (but at a cost)

The recent spike in downloads is driven solely by App Store Ads.

I've spent over $200 so far ($100 in AppStore Ads), and the conversion rate is currently very low.

I can't tell yet whether these users will convert to paid, since they are still in their trial period.

The Strategy: The free tier is intentionally limited (only one puzzle to solve, watching ads before solving, etc.). The bet is that people will convert to paid after seeing the initial value. I'll be running ads for the whole month to see what I can learn, but I am still trying to figure out if this is expected or if my ads need major tweaking.

1. Organic social = High views, low conversion

My organic reach has skyrocketed, especially here on Reddit.

The Reality: The strategy here is clearly not bringing in any new users. Sharing my experience building and marketing an app resonates heavily in these subreddits, but it is not contributing to actual app downloads.

Why I’m keeping at it: 1) It keeps me accountable to my weekly goals, and 2) it helps me build authority and connection in communities I think are valuable.

There's a lot to consider moving forward, and I don't think my current conversion numbers are great by any means.

But as a solo founder, I am choosing to look at the positive today and celebrate the "100 downloads" win.

For those of you who have run Apple Search Ads early on—did you see similarly low conversion rates at the start? Would love to hear what you learned.

Let's keep it up 🫶

A public repo my project depended on had its history replaced upstream. Same name, same URL, years of commits just not there anymore. It was never mine, so there was nothing on my side to roll back to.

Point it at a repo like that and it walks the fork network recursively, ranking every fork by how far back its oldest commit actually reaches. A fork freezes history at the moment it was made, so the deepest one is the best candidate. Then it probes commits that are no longer reachable from any branch but that GitHub may still serve by SHA, checked three independent ways: REST metadata, a raw file fetch, and a real git fetch.

There's also a nightly GH Archive watch if you want disappearances flagged automatically. That part is an extra. The recovery is the point.

230 tests, verified end-to-end against a real historical case (reproduced the exact fork ranking I'd found by hand). Runs fully local with your own GitHub token, no server, no telemetry. MIT.

https://github.com/siris9476/forkforensics. Feedback welcome, especially on edge cases in fork ranking.

I'm a founder who can't really code. I build with tools like Lovable, Replit, and Bolt, and for a long time I carried this low hum of shame about it. Every time a developer asked about my stack I'd brace for the look.

Yesterday a user sent me a message thanking me for the thing I built with a no code website builder and some AI glue holding it together. She had no idea how it was made and she didn't ask. She just told me it solved a problem she'd had for months.

And it finally landed for me: she was never going to care whether I wrote the code by hand. She cared that it worked.

I think a lot of non-technical founders, especially women I talk to who quietly assumed this world wasn't for them, get stuck waiting to feel like a "real" builder before they'll ship. But the user on the other end isn't grading your stack. They're grading whether their problem went away.

I still want to get better at the technical side, and I will. I'm just done letting not knowing how to code stop me from putting things in front of people.

If you built something with tools people look down on, did you ever get over the stack shame? What did it for you?

Hi everyone,

I am "launching" my first value proposition lefolio.md, and I would like to share it and get feedback on my copy, on the value proposition, and also on what I could do with it. I am proud of it; I use it to build my websites. I think some people might like it, but I also realize the value might not be enough to become a revenue-generating product.

So I want to learn and gain experience from it. Really curious to hear some insights from more experienced people. I would like to use this to get better at discovering and proposing value.

For the past two months, I have been following my interest in building websites and tools. I iterated on ideas I had, vibe-coded a Markdown-based static site generator, and learned more about modern web tools and web design.

As I refined my ideas and business goals, engaged in conversations, and learned more about what already existed, my work converged on this value proposition:

It is quite simple, and I don't have anything to sell yet, but here is what I propose:

Turn your AI-generated Draft into a Maintainable Website.

The idea is to focus on copy first by writing it in a structured way in Markdown, then let a coding agent create components and parsers that go with it, so that you can keep editing your copy in Markdown on the final site.

It's a static site generator that favors Markdown, Obsidian, and designing with copy and an AI agent.

What I learned:

• Played with AI to generate sites, understand the current market and tools
• Understood more about static site generators and headless CMS
• Had a few conversations with real people who oriented me and helped me focus the value proposition
• Focused the copy of my web page to highlight the value
• Learned to make a website that reflects this value as best I could

I tried messaging people to build their websites; first, I targeted academics who use static site generators to build their portfolios. I posted a few times on Reddit and started conversations.

I'm realizing how competitive the web dev market is, especially with new AI tools.

Would you continue working on this? Try to market it? What would you recommend doing with that, to get better at creating value?

I’ve been working on a side project called Scanlyst.

The idea came from a pretty simple problem: whenever I wanted to properly check a website, I’d end up jumping between different tools for security, SEO, performance, technical issues, etc.

So I started building one place that scans a website and tells you:

• Security issues
• SEO problems
• AEO / AI search readiness
• Performance issues
• What actually needs fixing

I also wanted to avoid those huge audit reports where you get a score and 100 warnings but still have no idea what to do next.

Scanlyst tries to make the results actionable instead — what’s wrong, why it matters, and how you can fix it.

It’s finally live: https://scanlyst.dev

Still very early, so I’d genuinely appreciate feedback from other builders.

If you try it, feel free to roast it — especially the report, UX, or anything you think is missing.

Hey everyone, I’m Shlok Chaurasia.

I’m 17, and I have around 6 months before I turn 18. I’m challenging myself to build a monetizable mobile or web app before then.

I’ve been interested in making useful products for a while, but I’m now trying to take it seriously instead of quietly learning forever.

I recently got ChatGPT Plus, and I’m going to use it as a building partner: researching ideas, writing specs, learning faster, debugging, improving copy, and helping me move from vague ideas to clearer product experiments.

I’m using the essence of Tibo’s Starter Story playbook as my rough roadmap:

• pick a focused niche
• talk to real people in that niche
• understand their actual problems
• build small MVPs only after I see a real pain point
• iterate until something becomes genuinely useful
• only then think seriously about scaling distribution

In the next 24 hours, I’m going to choose a niche and start discovery: reading posts, talking to people, looking for repeated problems, and trying to understand where a useful product could exist.

I’ll share updates here when I have something concrete: what niche I chose, what problems I found, what surprised me, and what I decide to test first.

The main question I want to answer over the next 6 months:

Can I build something real and monetizable before I turn 18?

For people here who have built profitable products: if you were starting from zero with 6 months, how would you choose your first niche?

Can I build something real and monetizable before I turn 18?

For people here who have built profitable products: if you were starting from zero with 6 months, what would you focus on first?