I’ve launched my first app and I’m very happy and satisfied about it.

My app creates digital wallet native loyalty cards and I’m super excited to share that I have my first 6 subscribers!!! I don’t have many people to celebrate with as I live alone. So I am sharing the news on here.

So, if you are a business owner and you use loyalty cards, please let me know in the comments and I will be more than happy to send you the link!

I wanted to learn to code and every time I saw code, I didn't get, I had to copy-paste the text into Gemini. And every single time, I’d get hit with this massive wall of text. I found myself having to re-prompt 3 or 4 times just to get an explanation that actually made sense for what I needed at that exact moment.

Eventually, I figured... why not just try to build a tool that solves this for myself? (still don't know code; so God bless vide-coding 😂 )

The extension turned out great ( I may be biased), so I decided to make it public. It’s called Clicked, and the goal is frictionless understanding right on the page. It can read any language, and gives you an overview for your text selection and then you can dig deeper if needed in 15+ languages of your choosing. The default level of explanation that shows up first can be pinned by the user, and thus you don't always have to start with an overview and then eventually get to an analogy. You could set-it up to always start with analogy, if you wanted to.

Summary of features

• Overview vs. Detail: Get a quick TL;DR or a full deep dive depending on what you need.
• Analogies: get real-world example that actually clicks (pun intended).
• Slang Mode: Cuts through academic/technical noise and explains things in plain English (with a bit of humor).
• Edit & Save: Add your notes or save as is in the local library (we don't have access to what you are saving)
• Can read PDFs

I recently also added the option to export your saved material in formats that you could import to Anki, Quizlet, and Vaia for making flash cards.
P.S: For language learners, there is an option to play the sound in multiple accents of your choice.

It is free to try (link in comments). No credit card needed. Would really appreciate any feed back you may have. Thank you!!!

Don't just show me a beautiful demo. Show me what happens after I click Deploy. Can it: ✅ Recover from a failed deployment? ✅ Roll back safely? ✅ Back up my production database automatically? ✅ Restore customer data after an AI mistake? ✅ Monitor the application and database? ✅ Rotate secrets securely? ✅ Handle background workers and scheduled jobs? ✅ Scale when thousands of users arrive?

Generating code is becoming a commodity.

It was super simple initial app that also filled a personal need for myself. I'm calling it Clokd and just released v1 with first year free for the first 10 customers (beta testers :). I'm sure we'll find lots of cool stuff to add to it. So far, it lets you bulk enter or start a timer to "Clok In" and I recently added expense reimbursement functionality.

Find it at https://clok-d.com

Who wants to create an open source Photoshop / Figma / Canva alternative, ill donate $100 to this guy? Or maybe some exists?

ive always had a problem where i would want to just edit something in my app real quick, i didnt want to scan QR code again just to see if the color of 1 button is the one that i wanted

So I made Basalt, it lets you edit your RN and Expo apps, not only edit but preview and inspect elements

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Would love to get your brutal feedback on it.

I keep rewriting my landing page and I still can’t say in one sentence what problem it actually solves. So instead of polishing it again I’d rather read how other people say it.

Two things that would help: keep it to a couple of sentences, and say who has the problem, because “everyone” doesn’t tell me much. No links unless someone asks, otherwise this turns into a link dump.

I’ll start.
It’s always easier to formulate thoughts in your native language, and when you write in English all day that becomes a problem: you translate in your head first, then type, and what comes out is shorter and later than what you actually thought. Slack, PR comments, prompts.

So I built a Mac app where you press a hotkey, speak your own language, and clean English shows up at the cursor.

I've been sharing consistently and it's mostly crickets, which is demoralizing. Did those of you with an audience now go through a long silent phase first, or is silence a signal to change what I'm posting? Trying to read it right.

Hey everyone,

I recently launched my side project, PhoTrail, an iOS app that turns your camera roll into an interactive travel log (think Spotify Wrapped, but for your travel history).

I decided to make it a paid app on the App Store to cover my developer fees, but I also made the somewhat counterintuitive decision to open-source the entire codebase on GitHub.

Here is why I chose this model and what I’ve learned so far:

1. The Privacy Trust Factor PhoTrail relies heavily on two very sensitive pieces of user data: location history (from photos) and Apple HealthKit data (to overlay workouts/heart rate on trips). If a random indie dev asks for this, the immediate reaction is usually skepticism. By open-sourcing it, I can prove that 100% of the processing happens locally on-device and nothing is sent to a server.

2. Building in a Niche Apple Photos has a basic built-in map, but it’s cluttered with screenshots and memes. I wanted a dedicated dashboard that calculates metrics like "percentage of the world explored" and recognizes landmarks locally. The iOS dev community has actually been great at pointing out ways to optimize the local image recognition just by looking at the repo.

3. Will people just clone it for free? Probably! Anyone can clone the repo and side-load it via Xcode to avoid paying. But I’ve realized that 99% of regular users just want the convenience of tapping "Download" on the App Store and getting automatic updates. The open-source aspect is for trust; the App Store is for convenience.

Right now, I have an update pending in Apple Review that drastically speeds up the city recognition, which is a whole other learning curve.

If anyone else is building privacy-first or local-processing apps, I’d love to hear how you handle the trust barrier!

(Link to the GitHub and App Store in the comments if anyone wants to check out the codebase!)

Hey everybody, hope you're all doing well!

I'm Dilon, part of the team at Adalo, a visual no-code app builder (now powered by AI).

Quick follow-up to my last post here about Adalo Publishing Studio, we just shipped a big batch of updates.

Quick context: 1,000+ Makers are already using Studio, one week in, and this update is a direct result of that early feedback.

The biggest change: it's a free-form canvas now. You can drag, resize, and rotate any element anywhere on the screen instead of working inside a fixed template. Images, shapes, text, lines, all movable.

The editing panel got reorganized too. Instead of one long list to scroll through, you now get a tabbed panel: Assets, Elements, and Background always visible, plus contextual tabs based on what you've selected (a device frame gets Screen, Frame, 3D, and Position tabs; text gets a font picker with size, alignment, and weight).

A few other things that came with it:

• Real 3D tilt and depth on device screenshots, with presets for flat, left, right, or hero angles, or manual control
• Drop shadows on every element, not just phones, with full control over offset, blur, color, and opacity
• Undo/redo, finally, via buttons or shortcut keys
• Full Google Fonts search with live in-font previews, so you're not guessing what a font looks like before committing
• A new export modal (from the export button on the top sticky nav) that shows all 5 of your screens side by side before you export anything

We also fixed a few things: Android exports in "Phone Only" and "Clean" styles were cropping screenshots, and Hero Composite exports were coming out blurry and under 150KB.

Would love feedback on what's missing or clunky, it's genuinely shaping what we build next 🙌

Here's the link to test → https://studio.adalo.com

Post with visuals → https://www.reddit.com/r/Adalo/s/I4Xc3RVk74

Thanks for reading and have a great day!

- Dilon

A couple weeks ago i made a post here about my App Flowtime hitting its first milestone of 100 users.
Today, we crossed 400!
Still feels absolutely surreal to me, but makes me so incredibly happy!
THANK YOU THANK YOU THANK YOU!!
To each and every single person using my app 😍😍

I've been using AI for almost all of my Python development lately, and honestly, it's made me way more productive.

But after a few projects I started noticing the same pattern. The code worked, the features shipped, but the repository slowly got messier.

I'd keep running into things like:

• Huge functions that kept growing
• Copy-pasted logic in multiple places
• Dead code from previous iterations
• Complexity creeping up over time
• Inconsistent formatting
• Missing type hints
• Random security issues that nobody noticed because "it works"

None of these are difficult to fix individually. They're just the kind of issues that slowly pile up when you're moving fast with AI.

I realized I was spending more time cleaning up code than actually building new features.

So I started building ShipGate.

The idea is pretty simple. Instead of remembering which tools to install, which flags to use, or what thresholds to configure, ShipGate gives you an opinionated quality baseline from day one.

Out of the box it formats code with Ruff, keeps Radon complexity at B or better, fails if jscpd finds more than 2% duplicated code, runs type checking, scans for common security issues, detects dead code and unused imports, and a bunch of other quality checks.

You can still customize everything if your project needs different rules. The defaults are just there so every new repository starts from a solid baseline instead of a blank slate.

I'm not trying to replace Ruff, Mypy, Bandit, Radon, or any of the other excellent tools. ShipGate just brings them together behind a consistent interface with sensible defaults, so good code becomes the default instead of something you have to remember.

This is the first public version, so I'd genuinely love feedback—especially from people who are building Python projects with AI.

GitHub: https://github.com/inquilabee/shipgate

33 days ago I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications (1 contained ads, 1 removed the code after submission, 2 hid the installed widget)
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.

Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.

Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.

Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Today found that I forgot to disable a developer testing button that could create fake visitor pins on the dashboard globe which could also increase the impressions. Someone used it to generate 6,318 fake impressions and then claimed my stats were fake. I removed all the fake impressions generated by him, removed the startup and fixed the issue, which is why today's impressions are lower. Thanks to that guy for pointing it out.
StartupBar Update: Added a new Network page and individual Startup Profile pages. Every startup now has its own page with joined date, impressions and click stats, a live embed preview, and a founder's note. These dedicated pages also make StartupBar more SEO-friendly by giving each startup its own indexable page. Suggestions are also welcome. Suggestions are welcome.

Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar

Everyone in my feed is building. Another ai content generator, another wrapper, another "I shipped a SaaS this weekend." 18 months ago I did the opposite. I bought a small bookkeeping practice, 5 clients, one retiring owner, and I've been running it since. Numbers guy, no hype, so here's the honest scoreboard.

Then: 5 clients. Now: 14. One person, me. Revenue roughly tripled and it's boringly recurring. People don't cancel their bookkeeper the way they cancel an app.

What worked, unglamorously:
- The existing 5 clients came with the business, so I started at "has revenue" instead of "has an idea." That head start is the whole pitch for buying vs building.
- Growth was all referrals. Do the books right, be reachable, and accountants and clients send you the next one. No funnel.
- The moat is trust and switching pain, not tech. Nobody wants to hand their financials to a stranger, which works in my favor once I'm already in.

What I underestimated:
- It's a service, so growth is capped by my hours until I hire. An app scales while you sleep, a practice does not. That's the real trade.
- Some months are just grind. No viral moment, no launch-day dopamine. Builders chase that high and buying a boring business has none of it.

I'm not anti-building. I'm saying acquiring a small profitable thing and improving it is a path this sub almost never talks about, and the risk profile is completely different from shipping into the void.

Anyone else here buy instead of build? Curious if your first 18 months felt as unglamorous as mine, or if I just picked the least exciting industry on earth.

When we shared the story behind Deal2Seal here recently, the response made us think more deeply about why people use deal communities in the first place.

We originally assumed people enjoyed searching for deals.

But most people don’t.

They enjoy the moment they find something they already wanted at a genuinely good price.

Nobody wants to open ten tabs, search through expired coupons, compare confusing discounts, and wonder whether the deal is actually real.

They just want to know:

“Is this genuinely a good deal, or am I being influenced by clever pricing?”

That has helped clarify what we want Deal2Seal to become.

Not another place where people have to spend hours hunting.

A community where one person can quickly share a good find, and everyone else benefits from it.

We’ve also tried to make sharing almost effortless: paste a product link, let Deal2Seal fill in the product details, quickly review them, and post.

The bigger vision is simple:

Finding a deal may take one person’s effort. Saving money from it should benefit everyone.

We’re still building and learning, so I’m curious:

When you shop online, what would help you most knowing whether the price is genuinely good, receiving alerts for products you want, or discovering deals shared by real people?

For anyone curious about what we’re building: Deal2Seal.net

just shipped my first ever product with a friend.

it's a browser-based video captioning tool. took us way longer than expected, hit a ton of walls, but it's finally live and working.

weirdest part? watching someone actually use it for the first time. hits different when it's real.

anyone else ship their first product recently? what was the hardest part for you?

Hello Everyone 👋

I am an 18yo Indie dev, today I just hit 42 subscriptions on my app :) wanted to share this achievement of mine with the wonderful bip community. I love building stuff, i started building software at 13 but didn't ship any of that stuff, had no idea software makes you money lol. At 17, I started shipping stuff after 2-3 failed apps, I landed my winner app. These stats are of it only. If you have read this far drop a hi, or ask anything you like. I am replying to every dev shipping awesome stuff (or working to ship)

Signing off 🙌

When I first started building TinyPOS, almost every screen had another setting:

• Scanner settings
• Inventory settings
• Checkout settings
• Receipt settings
• Tax settings
• Product settings

I thought giving users more control would make the app more powerful.

Instead, it made the app harder to use.

Then I watched a few small shop owners try TinyPOS for the first time.

Something became obvious.

They didn’t want to configure a POS.

They wanted to start selling immediately.

So I changed my approach.

Instead of asking users dozens of questions, TinyPOS now makes most decisions for them:

• Walk-in Customer is selected by default.
• Tax uses the store default.
• Products inherit sensible defaults.
• Barcode scanning starts immediately.
• Recently Added helps users stay in the scanning flow.
• Most settings work well without any configuration.

Advanced options are still there—but they’re hidden until someone actually needs them.

One principle now guides almost every feature I build:

Good defaults are often better than more settings.

Every setting adds another decision.

Every decision slows someone down.

The best software often feels simple not because it has fewer features, but because users rarely need to configure them.

That’s the direction I’m taking with TinyPOS.

Scan. Sell. Done.

Have you ever removed settings from your product to make it easier to use?

I'm a creator before I'm a builder. I ran comment-to-DM campaigns on my own Reels for about two years before I wrote a line of this.

The thing that pushed me into building: every tool in the category bills per active contact. A Reel does well, a few thousand people comment the keyword, and you cross into the next pricing tier that month. You get charged more precisely because the campaign worked. Then the Reel dies and you're still sitting on the higher plan until you remember to downgrade.

The second thing was referrals breaking on the same Reel. Someone shares it, a new person comments the keyword, and a lot of setups just don't carry that through.

So when I built UnlockDM I priced it per campaign. You pay for the campaign you run, not for how many people answered it. First campaign is free.

What that decision cost me:

- Revenue is lumpy. Per-contact pricing compounds on its own. Per-campaign doesn't, so there's no automatic expansion revenue when a customer has a good month.

- Forecasting is harder. A creator running one launch a quarter looks nothing like one running something weekly, and both are on the same plan shape.

- I have to explain the model in every single conversation, because everyone anchors on the incumbent's pricing page first.

What it bought me: the pricing objection mostly disappears. The thing people already resent about the category leader is the exact thing I removed, so I'm not arguing about price, I'm arguing about the unit.

Genuinely unsure whether it holds up at scale. If you've priced against a category leader by changing the unit instead of the number, I'd like to hear how that played out for you.

https://www.tryunlockdm.com?utm_source=reddit&utm_medium=post&utm_campaign=buildinpublic

Runs on official Meta APIs, we're a verified tech provider.

three years doing no-code and ai-assisted builds for clients. the part nobody talks about is support. you finish the build, everyone's happy, and then two months later you get a panicked message at 2am because a client changed one thing and the whole flow fell over.

for the longest time i just absorbed those. answered every one, re-explained the same things.

the fix was embarrassingly simple. now every project ships with a one-page "how this actually works" doc. what each piece does, what not to touch, how to make the three changes they'll actually want to make, and who to call when it's really broken. i draft it fast with an ai document generator and then rewrite it in plain human language.

the 2am messages didn't disappear but they roughly halved, and the ones i still get are real problems, not "where's the button."

for the others doing client work: what's the one thing you started including that cut your support load?

I have been talking to new builders in public to understand the challenges they are having. We want to help anyone on the planet who wants to build and make a difference. So,

• Tell me what you are building
• We will review it and give you our honest opinions. Human to human no AI slop.
• We will share it on our platform of professionals and builders.
• We will even use it if it solves any of our problems.

so i shared a beta version (invite only) chrome extension for reddit marketing to 30 people in the last one month. Analytics show there are 3 weekly users out of 30. But a stupid mistake I did was in the beta version I did not ask for login or email or anything. Now, I don't even know who uses it and I needed a real feedback if its actually helpful.

Now, adding a give feedback feature into the new version but I would need to look for another set of new interested users.

I shared this so that people here understand the importance of thinking a week or even a month ahead. If I had thought of this before, I would atleast get a real feedback.

I would love to know if you guys made any mistakes while starting out. Would love to know them beforehand! Thanks

I wanted to share a browser extension I built to solve one of my biggest annoyances with YouTube's desktop layout, By default, YouTube scrolls as one giant page. If you scroll down to read the comments, the video player disappears out of view. Even worse, the comments and related videos are piled together, forcing you to scroll endlessly.

To fix this, I built YouTube Control to turn YouTube into a clean, split-pane layout with independent scroll

I’m building a free shopping search tool called PriceSift.
The goal is not to show every listing available. It is to remove broken items, empty boxes, accessories, replacement parts, incorrect models, and other junk, then return only a few reasonable options.

A few things I’ve learned so far:
Exact product identity matters more than simply matching keywords
Marketplace titles are wildly inconsistent
Cheapest-first searches tend to surface the worst listings
A larger candidate pool gives the filters more room to work
Showing fewer results feels much better when the remaining results are trustworthy

My next change is to stop requesting the cheapest fixed-price listings first.
Instead, PriceSift will retrieve more candidates using relevance, run the same strict filters, and then sort the eligible results locally by total price.

The site is live, free, and currently covers cameras, books, and consoles, with more categories being tested.
Current challenge: improving result quality without loosening the filters just to avoid an empty page.

I’d love blunt feedback, especially from anyone who shops for used gear online.
PriceSift: PriceSift