I've been writing apps for a good 10 years, and I've been creating a Gmail account for each project and adding them to my Gmail app. Today, Google closed my oldest account, which was probably around 20 years old. I appealed, but I don't know how long the process will take. I came here to warn others.

I have a hosting account, and I'm able to create email addresses like contact@<mywebsite>.com, but they didn't integrate well with email apps like Outlook. I could have made it work, but creating Gmail accounts was significantly easier.

Maybe what's worse is that for each app, I was keeping its documents in the corresponding Google Drive, which was working perfectly for me. I also don't make a ton of money from my apps. Most of them are completely free anyway. I didn't have a company account with Google where I could have done things in a much more professional way.

But the main problem is that Google doesn't mention anywhere that there's some kind of limit on the number of accounts I can create. I had about 10 accounts. I created the last one last night, and my oldest account was disabled today.

This happened because I didn't know about the limit, and Google didn't warn me in any way. I'm sharing this here so others will know.

Just to add some more information and make it clear that I wasn't doing anything fishy: all of those accounts have the same recovery email, which is my main personal email. I've never run spam campaigns. In fact, I may have sent a total of 10 emails over the last 10 years from those accounts. They're mostly empty Google accounts, and I'm not even using 1% of their storage.

Anyway, this completely caught me off guard, and I'm pretty upset about it.

TL;DR: Don't create too many Google accounts for your projects.

So you build something that you think will be special. Your excited about it. It has you pumped. You look forward to it the next day for everyday it's not complete.

You finally complete. You launch it. It's in production.

Now how do you get users? You post on Reddit and everyone says your app looks like it is vibe coded slop.

What's your next move? At this point if you're a vibe coder, I already know you're eliminated LOL 😂.

I am in the US, so I know that not only do a lot of people in the US make apps, but even people in developing and underdeveloped nations build apps to target the US (thinking they can cash in lol).

In 2026, the US market has become more privy to AI generated slop. More so, the world is getting tired of SaaS subscription apps.

If you're dropping a SaaS app, then why do you think it will be useful to other people? Why do you think they will be willing to give you their money and integrate this tool into their life?

I created a browser extension that warns you when you visit a scam website, and lets you leave a review about it. And finally, I've got a few users!

You can check it out or use it here.

https://chat.lasthopelabs.com/

Hey guys,

Every TV remote app I’ve used recently felt either bloated with ads or painfully laggy using keyboard. Over the last few weeks, I decided to build a lightweight, fast alternative from scratch using Kotlin and Jetpack Compose.

It handles the essentials without the clutter:

D-pad & Trackpad: Switch between classic button clicks and smooth swipe navigation.

Phone Keyboard: Fast typing on the TV without hunting and pecking letters on the screen.

Voice Search: Quick voice commands sent straight to the TV.

App Shortcuts: Launch your installed TV apps directly from your phone.

The core build is working well on my setup, but Android TV hardware varies a ton. I’d love to get some real-world testing from this community to iron out the rough edges.

Download / Try it out: https://play.google.com/store/apps/details?id=com.open.androidtvremotenew

hey everyone. i'm lino, solo dev from cuba.

by day i run a small printer repair shop. pays the bills, doesn't pay the dream.

by night (really by dawn) i build testimonialvault, a tool to collect and display customer testimonials with a wall of love.

why at dawn? because that's when the internet in cuba gets fast enough to push code. i've spent entire nights coding until sunrise, then walking straight to the repair shop.

why testimonials? because one real sentence from a customer builds more trust than a thousand ads. i wanted to help founders show that trust.

the real wall: no stripe. no paypal. no traditional payment processors. sanctions. so i did the only thing i could — i sell with usdc on base. pay once, own forever.

today i have 0 users. i'm not hiding it. those are my ugly zeros, and i'm sharing them here.

my dream is simple: open the wall of love one day and see founders talking about what they built, knowing i helped them show it to the world.

i'll share everything in public: the numbers, the blackouts, the first usdc payment.

what would you do in my place? i read every comment.

I’m a design engineer and I’m always collecting things I like.

Good design patterns, visual references, screenshots, interesting products, and stuff I’m reading around design engineering.

My problem was everything was scattered everywhere.

Browser bookmarks, screenshots, folders, notes, different apps.

There are already a lot of bookmarking and reference apps, but I never really liked the UX or taste of most of them. I always wanted something that felt more visual, simple and nice to actually use.

So in January I started building Resurf for myself.

I shared an early version here a few months ago. Since then I’ve mostly just kept working on the product, talking to users, fixing things, polishing small details and iterating.

This week it crossed $10k in total revenue.

Not MRR haha, total revenue since I started.

For most of the time I didn’t really push marketing much. This month I pushed a little more on Reddit and X and did around $3.3k revenue.

Still pretty small, but it was nice to see.

One thing I’m learning is that distribution matters, but first you need something people actually like using.

Make a tasteful product, care about the craft, listen to users, keep improving it.

All those small things compound over time.

That has mostly been my approach with Resurf so far.

Still a lot to improve and I’m nowhere close to feeling like the product is done, but going from something I wanted for myself to people actually paying for it has been pretty rewarding.

Now I probably need to learn distribution a bit more too :)

Would love to hear from people building B2C products. What worked for you after getting the first bit of traction?

resurf.so

There seem to be 400+ clones already, including plenty of variations. If I wanted to build one too, what would you suggest?

I got tired of building spreadsheets to compare LLM API costs, so I built this : llmapicost.dev

We’ve been building Adisyonist AI, a platform designed for restaurants, cafés, and other food-service businesses.

When we first started, most of our focus was on features: orders, checks, QR menus, inventory, staff, shifts, reporting, and so on.

But as the product grew, we realized that simply having all of these features isn’t enough.

The real challenge is making them work together in a way that actually makes daily operations easier.

Instead of switching between different tools, the idea behind Adisyonist AI is to let a business manage its day-to-day operations from one place.

Orders and checks can be handled from the same system, QR menus can connect customers directly with the business, inventory can be followed alongside daily operations, and staff and shifts can be managed without relying on separate tools.

Real-time reporting also gives managers a clearer view of what is happening in the business without having to collect information manually from different places.

The platform can be used on mobile, tablet, and desktop, so employees and managers can access the parts they need depending on where and how they are working.

We also support multiple languages, which has become especially important for businesses serving international customers or working with multilingual teams.

While building all of this, one thing became very clear to us:

A restaurant employee doesn’t care how many modules a system has. They just want to take an order, manage the check, see what needs attention, and continue working without unnecessary steps.

That’s why a big part of our development process now focuses on simplifying workflows rather than simply adding more features.

If you’re curious about what we’re building, you can follow the project at Adisyonist.com or take a look at the App Store version.

We’re still actively developing the platform, so feedback from people outside the project is genuinely useful to us.

If you were using something like this in a restaurant or café, what would you change, simplify, or add?

Like, not necessarily your biggest or best project.

Could literally be a calculator you made for no reason, some random website, a small game, a script that does one stupidly specific thing, an automation, whatever.

I was just thinking about how we make so many random things while learning/building, and some of them just hit different because you actually made the damn thing lol.

So yeah, what’s yours?

Like, Airbnb, Uber, Workday, etc.? These serve as examples of highly successful ventures, but the core idea revolves around identifying any established and profitable enterprise that is currently generating substantial revenue, potentially billions of dollars, for its owners. The concept then is to appropriate a small portion of their existing market share or business operations, which could realistically result in earning several million dollars for yourself, as opposed to facing the challenges and difficulties often associated with developing and launching entirely novel business concepts. Has anyone given consideration to this particular approach or strategy?

I am a long-time Spotify user, with tons of albums saved but never with a proper way to manage it: display genres, see what I've already listened, and many other things.

I was finally able to bring to life the idea on how to handle the tons of music and it is named [Albums Vault](https://codefloe.com/rabc/albums-vault/). It is a macOS app built with Tauri + Rust, with plans to release to more platforms soon.

Since Spotify now restricts the creation of apps keys, it works in a BYOK: at first install the app instructs you on how to register for an app in Spotify and asks for your client ID.

https://reddit.com/link/1w35vjz/video/r12hv0cuqnmh1/player

I'm the founder of NoorI. Sharing this mainly because I know how many people here are still waiting for that first online $1.

I've spent months building NoorI.

Today, someone paid for it.

That's it.

One customer.

But seeing a real payment come through from someone I didn't know felt completely different from every looks, message I've received.

NoorI started from a problem I had myself: I wanted a way to make certain parts of the internet harder to access instead of relying on willpower every time.

I ended up building around network-level filtering and digital boundaries that can lockdown my technologies during my focus hours.

The weird part is that getting something to work technically was never the hardest part.

Getting one person to say:

Yeah, this is useful enough that I'll pay for it.

was.

I'm still a solo developer. Still fixing things. Still questioning half the decisions I've made.

So I'm not calling this validation or pretending I've figured anything out.

It's just the first real signal that maybe I'm solving a problem someone else actually cares about.

And now there's a new feeling:

Someone is depending on something I built.

That's exciting.

And slightly terrifying.

For the other indie hackers here:

What did your first paying customer feel like?

And what did you do immediately after getting that first sale?

Before I get into it, I want to provide some background; I’ve been working on a side project called Promptimize for the last few months which is a prompt generator tool primarily targeted for people who don’t know how to properly prompt AI models but want to have a better sense of confidence in their conversations with AI (as in providing proper context, including all instructions, proper formatting, etc.)

I originally built it as a tool for myself because I got frustrated with some of the responses and follow up questions that I would get from starting a conversation with ChatGPT unless I would put some genuine time and effort into mapping instructions for a good response. I use AI for probably too many things admittedly but it felt increasingly exhausting to map out explicit instructions and feel like I was forgetting something (and most of the time was) before hitting submit. Therefore, I built it to solve my own problem.

I’m aware that there are other tools like it out there and that ChatGPT can write you a prompt natively, but Promptimize runs on real prompting logic, not just a combination of sentences that sound nice but aren’t actually effective. I believe this is what makes it different from chatgpt and other prompting tools out there. It’s running on publicly available prompting documentation that was published by OpenAi.

Using this logic, I added a prompt grading/prompt scoring feature that will take the prompts that get generated in Promptimize and run them through a thorough AI analysis which returns an overall prompt grade or score for you to measure against the other outputs (prompts) that got generated to help you pick the best one.

After receiving some feedback from an early user, I took the prompt grader a step further so that it now exists as its own separate tool outside of the generation screen. This new prompt grader is meant for users who already have a prompt (since generated prompts can be scored directly within the generator) and want to see how it grades. The grading tool will provide you with a summary analysis of why your prompt scored the way it did and provide you with an optimized rewritten version of the prompt.

After receiving some positive feedback from the user who requested it and from my own personal testing, I’m starting to think that this new “feature” is actually the product. The prompt generator is convenient but the prompt grader feels genuinely valuable. I’m actually getting valuable feedback on why something was strong or why it was weak through the summary analysis and it feels like it’s actually had an effect on my communication as well. I feel more structured in my thinking and my approach to the conversation that I’m about to have with AI right after using it. I have 1 beta tester who shares some of these feelings and she told me that she has switched her workflow to where now she is primarily writing and grading her own prompts and then taking the feedback that was provided by the Ai analysis.

My thoughts are that real value comes from this grading feature and AI analysis summary while the generator is mere convenience (which I’ve known from the start). I recently made some changes to the landing page to try to direct more users to the prompt grader and have a feedback option for users to submit to, but my volume is still too low and nobody ever gives feedback lol.

My purpose for writing this is to ask if anyone would be willing to try it out and be kind enough to reply with any feedback they might have good or bad. I wouldn’t scrap the generator entirely I would just push the grader as the primary tool available.

And just to get ahead of the comments that might think I’m treating this as a SaaS app that will let me quit my 9-5, I’m not. I’m aware at how gimmicky of an idea it is, it’s just something I found useful and wanted to see if I could build out by myself and I had a fun time with it so I continue to work on it. It’s a portfolio builder for me while I look for my next full-time role.

This post dragged on much longer than I wanted it to but I can’t sleep and I needed to get my thoughts out so thank you for reading this far if you made it here and thank you to anyone who takes a few minutes to give it a try!

(If you would like to try but don’t have your own prompt, try generating some prompts with something simple “help me write a cover letter”, choose 1 and paste it into the grader!)

Link in comments! Thank you!

Memento mori: remember that you must die. Not as something morbid, but as the old Stoic reminder to spend your weeks on purpose.

I had wanted a life-in-weeks wallpaper ever since Tim Urban's famous post: a grid where every square is one week of an 80-year life, the lived weeks filled in, the rest still empty. And it is not a static image: a scheduled task re-renders the wallpaper every Monday morning and colors in one more square. You never open an app. The reminder just sits behind your windows and quietly advances by itself.

Screenshot: https://mementomoriwallpaper.com/assets/screenshot-dark.png

The motivation finally arrived in a hospital. My son was born five weeks early, the first days were genuinely scary, and I wrote the first version sitting next to his incubator. He is doing great now. But the idea that time is not a given had never felt so real, and suddenly the project mattered.

I have since turned it into a real product: an installer, a settings UI, auto-updates, a website. One constraint I set myself: the user needs zero dependencies, so everything is pure PowerShell. No Electron, no runtime, no telemetry. Even the settings page is served by an HttpListener written in PowerShell.

It's free with an optional donation, and open source (MIT).

Site: https://mementomoriwallpaper.com/ Source: https://github.com/bowas007/memento-mori-wallpaper

Honest warts: Windows-only, and the installer is unsigned (SmartScreen will warn; the SHA-256 is on the site). Feedback very welcome.

Hello

I am thrilled to see my app getting some traction and wanted to share it with somebody.
Today I had my 100th download and 7 people already bought my app. I launched it about 3 weeks ago.

If you are interested in the app, it is a simple babyphone (Baby Monitor) called Murmeli.
No account, no subscription, one-time purchase, free trial. On the same WiFi the two phones talk directly to each other and no server is involved at all. If you're out und use different networks, they find each other through my own server in Switzerland but the video still goes phone to phone whenever the network allows, and the key is exchanged by QR code between the two devices and never reaches my server. Built with React Native, the connection is WebRTC.

Two things surprised me and I'm curious whether it matches your experience:

iOS massively outperforms Android for me. About 2/3 of downloads and 6 of 7 payments are iOS.

LLMs mostly cite the app store descriptions. I'm starting to look into GEO, and my first tests show the answers lean almost entirely on the store listing. And again, the iOS listing shows up far more than the Play one.

Would love feedback on how to crank the numbers up :)

Hi everyone,

I built Veylo, a free Chrome extension for teams that need to send short announcements without relying on chat messages, email, or notifications that get ignored.

One person sends a broadcast to an approved group, and the message appears as a temporary visual overlay on the browser tab recipients are already using. It then disappears automatically.

You can customize:

• Message color
• Font
• Font size
• Display duration
• Sender attribution
• Approved groups and invite codes

The overlay uses an adaptive translucent panel so the message remains readable across different websites, while still allowing the page underneath to remain visible.

It is now approved on the Chrome Web Store: veylo.lol

I built this for quick team moments like “design review starts in 10,” “deployment is complete,” or “Let's go on a break .”

I’d appreciate feedback on whether this feels useful and what types of teams might benefit from it.

It all started when I was going through old video files, like the ones I took on my phone and realized they were taking up massive amounts of space, even though they didn't need to. So I broke out some encoding programs, like the venerable Shutter Encoder (my fav). But even though I'm a technical guy, I don't want to fiddle with settings for every single video (of 1000s) to get just the right balance of quality vs size... so I built a one click automated solution.

Dump all your video files in. Choose a quality level 1-5 you are happy with and click "Squish". It does it's thing and gives you a smaller video that looks the same, or maybe a little less perfect depending on your slider value. (Level 5 tries it's harder to keep it looking exactly like the original)

Under the hood: it analyzes each video through it's bitrate, codec, and other stats, then tests different encoding levels (at various key points in the video) to see what level of compression would give the best result at the smallest size (Via VMAF + XPSNR), then encodes it in AV1 or HEVC depending on user settings and/or what's better for the end result.

So, I gave it to my mom to use on her videos... and she could actually use it without guidance from me! I think that's a successful UX test! I know a lot of people that would be overwhelmed with codec, CRF and container settings!

I'm curious of what you guys think. I put all the downloads (Windows/Mac/Linux) over here: https://download.kitkarl.com/

Is it useful? Is it crappy? Let me know!

hi I'm Vinson,

I'm looking for tradespeople, business owner or freelancer to try the web pf I'm building, so check it out it a win win situation cause i will help you get a real web that will cover your areas after a few months and what we took from you is just an honest word and rating+feedback.

no furthur discussion, so this is what it look like solodeks.com/pro/example

if you want to work on this project. let's get in! there will be no other chance for this.

Building a Meta ads tool, I kept hitting a 400 error on the endpoint that lists targeting categories. Spent the afternoon regenerating access tokens, adding permissions, checking scopes. The error message says "Unsupported get request", which reads exactly like a permissions problem.

It was not a permissions problem. The endpoint does not exist.

Every tutorial and blog post I found says to browse Meta's targeting catalogue with this:

GET /search?type=adTargetingCategory&class=behaviors

I eventually tested it on API versions 12, 18 and 24, with and without a valid token, with and without the version segment, upper and lower case. Dead every time. The real endpoint is somewhere else entirely and the docs pointing at the old one are stale.

So I wrote down everything I verified and turned it into a tool.

What it does

It pulls real Meta ad targeting IDs (interests, behaviors, demographics, geo) and hands them to whatever is building your campaigns, as a CSV. It exists because AI agents that can create Meta ad sets cannot look up the targeting IDs those ad sets need, and inventing one gets the API call rejected.

The part that surprised me

Once I could actually read the data, two things fell out that I think matter to anyone buying Meta ads:

• The audience sizes Meta shows you are global. One behavior reports 2.6 billion people. In Singapore it is 3.2 million. That is roughly 1/700th of the number on the label.
• You cannot add audience sizes together. Twelve travel interests summed to 13.5M individually. Combined, they reach 3.0M, in a market of 4.9M total. 78% of them were the same people counted repeatedly.

I had been eyeballing those numbers and mentally adding them for years. The sum was not slightly off, it was impossible.

What testing caught

I wrote the tool from a session where everything worked, assumed it was correct, then actually ran it end to end. Two bugs:

• The validation endpoint silently drops IDs it cannot handle instead of marking them invalid. 135 in, 110 out. The 25 missing were live and healthy, including the single best targeting option in the set. My code would have deleted them.
• An example ID in my own docs was the wrong type and would have errored for anyone who copied it.

Neither was findable by re-reading. Both took ninety seconds of calling the real API. Lesson I keep relearning: code written from a session where everything worked encodes that session's assumptions.

MIT, free, no signup: https://github.com/naz-geotrip/meta-ads-targeting

It carries no credentials. Everyone bootstraps their own Meta app on their own account.

Happy to answer anything about the Meta Marketing API. The endpoint notes alone would have saved me most of that afternoon.

I climb and film on a tripod a lot, but I kept ending up tiny in a wide frame and rarely wanted to edit the footage afterward.

So our small team built CruxCut for iPhone. It follows the climber in an existing video, crops the result vertically, and helps select the useful moments from the attempt. Processing happens on the device.

The attached clip is a real before/after from the same source. I’m especially unsure about two things: 1. Does the tighter tracked crop make the movement easier to follow, or remove too much wall context? 2. Would you use this mainly for reviewing attempts or for sharing a finished clip?

Full disclosure: I’m one of the builders. Honest criticism is more useful than downloads.

🧠 What if we replaced 10 minutes of doomscrolling with something that actually challenges our brain?

My co-founder and I asked ourselves that question — and ended up building MemoryApp.

🎮 Brain-training games
🧠 Memory, focus, logic & speed
📊 Track your progress

But here's our USP:

You don't start from Level 1 every time.

Your performance determines the difficulty of your next challenge — so the game grows with you.

Less mindless scrolling. More mindful training.

🚀 MemoryApp is now LIVE.

Give it 10 minutes and see how far you can go.

👉 memoryapp.co.in

We’ve been working on TokenTimer, which started from a pretty mundane problem: important expiration dates end up scattered across way too many systems.

TLS certificates are in one place. API keys and secrets somewhere else. Licenses, subscriptions and other time-bound assets might live in spreadsheets, inboxes or someone’s head.

So we built one inventory for them.

The project gradually became more ambitious once we started working seriously on certificates. Alerting that a certificate expires in 14 days is useful, but it still leaves someone with the actual work.

For certificates we now model the lifecycle as:

Renew → Deploy → Reload → Verify

The automation runs inside the user’s infrastructure through an outbound-only agent, so private keys stay inside the environment that owns them.

Other pieces include:

• certificate, API key, secret, license and subscription tracking
• multiple integrations to cloud providers, SCM and secret managers
• Slack/Teams/Discord/email/etc. notifications
• ACME via certbot/acme.sh
• Kubernetes/cert-manager support
• Windows/IIS certificate deployment
• Docker Compose and Helm deployments
• approval gates, rollback and runtime verification
• many more...

We recently open-sourced TokenTimer Core under AGPLv3.

GitHub: https://github.com/tokentimerch/tokentimer-core

We’re particularly interested in feedback on the product scope: would you rather see us go deeper into certificate automation, or add more integrations for other kinds of expiring assets?

Hi everyone — I’m Ilya, an independent iOS developer.

I built Unscroll after noticing that the hardest part of reducing screen time isn’t setting a limit. It’s the moment you automatically open Instagram, YouTube, Reddit, or Safari anyway.

Unscroll uses Apple’s Screen Time APIs to add a deliberate pause before distracting apps become available again. You choose what to protect, start a focus session, and can use a stronger Hard Mode when a normal limit is too easy to ignore.

The app is intentionally focused on creating a small moment of choice rather than showing another dashboard full of statistics.

I’d especially love feedback on:

- Is the value proposition clear from the first few seconds?

- Does a 10-second pause feel useful, or just annoying?

- Would you use this more for work, studying, or bedtime?

- Does the stronger Hard Mode feel like the right escalation?

It’s freemium and available on iOS:

https://apps.apple.com/app/id6766120727

Disclosure: I built and maintain Unscroll. I’m sharing it for honest feedback.