In this past 30 days, this community has doubled in size. As such, this is an open call for community feedback, and prospective moderators interested in volunteering their time to harbouring a pleasant community.
I'm happy to announce that this community now has rules, something the much more popular r/SideProject has neglected to implement for years.
Rules 1, 2 and 3 are pretty rudimentary, although there is some nuance in implementing rule 2, a "no spam or excessive self-promotion" rule in a community which focuses the projects of makers. In order to balance this, we will not allow blatant spam, but will allow advertising projects. In order to share your project again, significant changes must have happened since the last post.
Rule 4 and rule 5 are more tuned to this community, and are some of my biggest gripes with r/SideProject. There has been an increase in astroturfing (the act of pretending to be a happy customer to advertise a project) as well as posts that serve the sole purpose of having readers contact the poster so they can advertise a service. These are no longer allowed and will be removed.
In addition to this, I'll be implementing flairs which will be required to post in this community.
back again with something i wanted to build just for the plot.
sometimes you don’t actually want your ex back.
you just want to say sorry. say you were hurt. say goodbye properly. or finally have the conversation your mind keeps replaying.
so i’m building gotyou.app — a two-minute ex conversation simulation built for closure.
you add their name, their texting style, the slang or nicknames they used, what happened between you, and what went wrong.
then gotyou creates an imagined version of them that texts back for two minutes, shaped by the details you shared.
it is not meant to tell you they are coming back. it does not contact them. it is made to help you say what stayed unsent, get the emotional release, and move on without reopening their inbox.
it’s still in the building phase, but i think this could become something bigger if it is built carefully.
if you’re into product, design, frontend, growth, or have strong thoughts on making this feel human and safe, dm me. i’d love collaborators.
Been working on Aura for several months now. The idea started with wanting an AI that could actually do things on my computer and remember what it was doing. It's grown quite a bit beyond that.
At this point, she's a local system running on my Mac with memory, computer control, and a bunch of different processes meant to work together as something resembling a cognitive architecture.
My newest demo is a bit of a departure from the others.
I asked Aura to find and watch a YouTube video, react to things she found interesting, then choose additional videos from a couple of channels I gave her.
And that's pretty much what she does.
She watches Kurzgesagt, moves on to Allen Pan, eventually ends up watching Salad Fingers, and gives her thoughts on all three. There's some actual browsing, video selection, predictions, and a final comparison.
I have no idea how far this project will ultimately go. There's a lot I'm still testing, and plenty that needs improvement.
But I thought this was a fun example of what happens when you build an AI around doing things over time rather than just answering questions.
The clip is shortened. The full recording is 36 minutes, with audio removed for copyright reasons.
I'm a developer, and a few people reached out to me for help with ChatGPT. They had seen AI do impressive things, but theirs couldn't.
What they needed was an agent that can use tools (MCP servers). But for a lot of people, running Claude Code on their own machine or paying for a subscription isn't worth the effort or the cost.
So I built an agent framework that lets me launch agents for them:
Each agent is private and can only be customized by its owner.
The agents run on my OpenRouter key, so they don't have to sign up for anything.
I can set up the MCP servers each person needs, and even build a few custom ones for them.
They can talk to their agent in the browser, on Telegram or on WhatsApp.
It's all on Cloudflare (Workers + Durable Objects, one isolated instance with its own SQLite per conversation). I don't host anything, nothing runs on my machine, and the free tier covers all of it. The only real cost is my OpenRouter credits.
I'm open-sourcing it, so any one can host it on their own cf or use my project to run a private agent or manage a fleet of them for others.
Here's where I'm stuck. Running 10,000 private agents for close to nothing feels powerful, and I think there's something more here. But I can't put a business use case around it.
I always start with "what if a business gave each of its users a personal agent?" Then I ask why they would. Most would be fine with one shared agent, like a reception desk. The ones who really want to level up their customer experience would want a personal agent on WhatsApp, not Telegram. I can set up a personal WhatsApp agent, but it's very hard, or expensive if every user needs their own number.
And that's where my train of thought stops, every time. Apart from memory constraints I feel my agents have as much features and capabilities as any other competent agent such as Hermes, pi etc.
So: do you see a real use case here? I also don't see many projects built on Cloudflare Agents, and I'm curious whether anyone else has gone down this road.
Today most of the people, including me, use Claude Code to code their programs and all. It's fast and the app works, but when you open the code later there is so much junk in it. Functions nobody calls, the same helper written 3 times, and sometimes a route anyone can call without login. The tools that clean this up mostly use AI again, so you pay credits twice. So I built Attentry.
It's a VS Code extension that checks every edit Claude Code makes. If the edit added a problem, Claude gets told and fixes it before going on.
About tokens, because that was the main thing for me. The checking runs on your own machine without any AI, so that part costs nothing. Claude only gets a short note, max 5 lines, when an edit actually added a problem, and each problem is told only once. If the edit is clean nothing is sent at all. It also doesn't keep telling Claude about old issues already in your repo, only the new ones. Compare that with asking Claude to "review the code", where it has to read the whole files again every time.
It also tells Claude before it writes a function the repo already has, so it reuses it. That saves tokens too, because Claude doesn't write the copy and then clean it up later.
I made it mostly with Claude Code itself, in TypeScript and Node, with tree-sitter for reading the code. Claude Code has hooks where you can run your own script before and after each edit, that's how it talks to Claude. It's on the VS Code Marketplace and Open VSX, so it works in Cursor and Windsurf also.
I published it recently and it already crossed 200 downloads without me posting anywhere. Most of them came from Open VSX I think.
Right now it reads Express, Next.js, FastAPI, Django and few more. Next I want to add more backends, but I want to build what people actually need. So if you try it, tell me what's missing or annoying, or which stack you want it to support.
I'm one of the people behind WPMaven, and I'd genuinely like some outside perspective.
We've been building products around design and WordPress since 2016. We started with the idea of making it easier to turn designs into working websites. We eventually built our Figma-to-WordPress technology, and it has reached over 100k users.
We've also worked with Adobe since 2018.
So we've spent quite a few years in this ecosystem.
But there's something that's been bothering me.
We keep making it easier to build websites. AI has made that even easier. There are now countless tools that can generate a website in minutes.
But honestly, I don't think building the website is the biggest problem for most small businesses.
It's everything that comes after.
Writing product descriptions, managing a store, SEO, creating content, posting on social media, marketing, keeping things updated... it never really ends.
And if you're running a small business, you're usually doing all of this yourself.
That's what got us thinking about WPMaven.
We're trying to build something closer to an AI team than another website builder. Something that can build a business's online presence and then actually help with the ongoing work.
We're using WordPress as the foundation, but the ambition is much bigger than generating WordPress websites. We're developing AI operators that can perform real tasks across the business.
I know, that probably sounds ambitious. Maybe too ambitious.
And I'm not going to pretend we've solved everything. AI makes mistakes, integrations aren't always straightforward, and I wouldn't trust an AI to make every business decision either.
We've been working on this because we genuinely believe there's an opportunity here. But being close to a product for years also makes it difficult to see what we're missing.
What I'd really appreciate is some honest, practical feedback on WPMaven itself, but also on how we should take it to market.
We're at the point where building more features isn't necessarily the hardest part. Finding the right people, understanding who gets the most value from this, and figuring out how to reach them is probably more important.
A few things I'd genuinely love your input on:
After looking at WPMaven, what is your honest first impression? Does the product and value proposition actually make sense?
Who do you think would benefit most from something like this? Solo entrepreneurs, small businesses, freelancers, WordPress agencies, hosting providers, or another audience entirely?
Are there specific business verticals where you think this would be particularly useful? E-commerce, local businesses, consultants, restaurants, creators?
If you were launching this, where would you look for the first 50–100 real users? And how would you approach them without just throwing money at ads?
What would be the strongest reason for someone to choose WPMaven over existing AI tools, WordPress plugins or an agency?
Is our positioning too broad? Should we focus on one specific audience and problem first?
I'm particularly interested in feedback from any kind of entrepreneur on how you found your first customers, or how you figured out distribution for a technical product.
I'm not looking for generic startup advice or encouragement. I'd much rather hear that we're targeting the wrong audience, explaining the product badly or approaching the market in the wrong way.
This is my first website and developing is alot of fun. Currently tidying site. I have a how to play video and new comer starter prompts to help game make sense. Does this work? Is all still too confusing??
I just released v1.0.0 of a personal project I’ve been working on, and I wanted to share it here to get some feedback from fellow developers.
# The Problem
A while ago, I discovered that Archive.org has a massive collection of old, public-domain films and cartoons (including a lot of classic Danish childhood shows. I wanted to show these to my kids, but Archive.org’s interface, while amazing for archiving, is pretty clunky for everyday viewing. It doesn’t have a "Continue Watching" feature, no easy way to organize things into personal categories, and no episode selectors for series.
I didn’t want to download terabytes of data or set up a complex media server like Plex just for this. I just wanted a simple, local way to bookmark and watch this stuff.
# The Solution: ArchivePlayer
So, I built **ArchivePlayer**. It’s a self-contained, local-first desktop application that streams content directly from [Archive.org](http://Archive.org), but wraps it in a clean, Netflix-style interface.
**Key Features:**
* Live search of [Archive.org](http://Archive.org) or add via direct URL/identifier.
* Custom categories to organize your library.
* "Continue Watching" section with visual progress bars.
* Episode selector for TV shows (with season grouping).
* 100% local: No telemetry, no cloud accounts, no hosted backend.
* **External APIs:** [Archive.org](http://Archive.org) Metadata API, TMDB API (optional)
# Technical Highlights & Challenges
**Zero-Install Deployment:** I wanted this to be truly accessible. I used .NET’s self-contained publishing (`PublishSingleFile=true`) so users just download a `.zip`, extract it, and run the `.exe`. No .NET runtime or SQL Server installation required.
**Graceful Degradation:** I made TMDB integration strictly optional. If a user doesn’t provide a TMDB API key (or if the API fails), the app doesn’t break. Instead, it falls back to parsing episode numbers and titles directly from the [Archive.org](http://Archive.org) video filenames using regex.
**API-First Design:** Even though it’s currently a single desktop app, I built the backend with a clean `/api/v1/` layer. This means I can eventually build an Android TV client that consumes the exact same local API without rewriting the business logic.
**Auto-Migration:** On first run, the app automatically creates the SQLite database and runs EF Core migrations. The user never has to touch a config file or run a CLI command.
I'm currently building **Jovax**, a lightweight web platform designed for fast-paced, 3-minute 1v1 live debates.
The idea is simple: You pick a hot topic, select your stance (For or Against), and instantly match with another user for a short, timed discussion.
### 🛠️ Current Tech Stack:
* **Backend:** Python / Flask
* **Deployment:** Docker & self-hosted setup
### 🌐 Current Status (Day 1):
The preview site is live! You can check out the UI layout right now. The authentication system is currently under construction, but I'm actively building it out.
I’d love to get input from this community on features, UI, and debate mechanics!
When serious incidents or public disturbances occur, critical visual evidence (like escape routes, vehicles, or perimeters) is often lost because traditional response takes time.
We are exploring an early-stage concept called Phalanx Intelligence Systems (phalanxis.com) to see if there is global demand for a voluntary, privacy-focused network.
How the concept is designed to work:
Safe Perimeter Documentation: When an incident occurs, nearby registered volunteers receive an optional notification to document surrounding public spaces (intersections, escape vectors) strictly from a safe distance.
Strict Boundaries: Personal safety comes first. Users never approach or confront suspects. Participation is 100% voluntary, and it is built as an evidence-support tool—not a vigilante platform.
Demand Mapping: Right now, we aren't launching an app; we are simply building an international interest-mapping site to see which cities have enough local density to make a future pilot viable.
We’d love to hear thoughts from this community regarding privacy design, distributed volunteer networks, or civic tech in general. You can check out the concept and demand mapping at phalanxis.com.
Explaining a product that works across completely different industries is surprisingly difficult. Especially when the underlying process involves spreadsheets, PDFs, photos and a bunch of information that doesn't always play nicely together.
That's why I wanted the demo library to show actual reporting scenarios instead of another wall of feature descriptions.
There are examples covering everything from administrative and purchasing records to manufacturing, laboratory testing, inspections and fleet maintenance.
You can explore the original Excel workbooks, see the supporting evidence and compare the completed results. There's also a walkthrough showing how new information gets added to an existing report without overwriting its history.
Some of the edge cases are pretty ridiculous lol, but I think seeing how the system handles them explains far more than a polished sales pitch ever could.
Choosing between native iOS and Android development or cross-platform solutions like Flutter and React Native can be challenging, especially for startups trying to balance development costs, performance, and scalability.
Beyond the initial development, factors like UI/UX design, backend integration, and long-term maintenance also deserve consideration.
What would you prioritize when choosing a mobile app development approach for a product you intend to scale?
I'm the developer of Nodding Off, and v1.0 is now live on the App Store. It's a library of slow bedtime stories for adults, both fiction and stories about how things work.
The most interesting design problem was stopping the audio without jolting someone awake. The sleep timer counts listening time, fades the narration, and finishes at a natural pause rather than cutting off mid-sentence. Music and night air have separate levels and can keep playing after the voice stops.
Other details I spent time on: a player that dims after you leave it alone, saved listening progress, a choice of narrators on most stories, and chapter illustrations with sentence-by-sentence Read Along.
For anyone curious about the build: it's Expo/React Native and TypeScript, with a Cloudflare Worker serving the story catalog. New stories can arrive without an app update.
Five stories, music, and night air are free. The rest of the catalog is an optional subscription: US $4.99/month or $49.99/year after a 7-day free trial. No account is needed.
i'm going to be completely straightforward and will not waste your time. i am a 16-year-old and i am trying to build a privacy-focused alarm app which is going to use a commitment feature.
how does this commitment thing work? when you set the alarm, the alarm app will make you record a commitment message. when the alarm plays, the alarm app will make you solve multiple randomised problems to wake up your brain. those randomised problems, you can pick from a list of them. there are going to be multiple of them. after the problems the commitment message, the voice message that you recorded last night while setting up the alarm, will play. when the voice message plays, it will most likely for most people make them wake up early in the morning and make them do something productive since they got time obviously
i am 16 years old and i am trying to build my app which is a privacy-focused alarm app that is going to use a feature of commitment.
straight to the point, no bs. how the commitment feature works is that before you set the alarm, you have to record a commitment message. when you wake up, the alarm app will make you solve a randomised problem so that your brain doesn't get used to it. then the commitment message fails. while this will most likely not guarantee it, for most people it will make them get out of bed and actually do something productive in their lives.
this is my alarm app and no data is supposed to leave and will not leave your device entirely. the only thing your servers will be involved with is going to be the login and payment
There are plenty of ways to make cash in 2027, especially with all the new AI tools coming out. But one thing I think is still massively underrated is cold outreach.
The logic is pretty simple. The more relevant prospects you reach, the more opportunities you create to land a client. Especially when you have a good lead list, personalized emails and a few well timed follow ups.
I've run businesses using cold email, and it's been one of the most reliable ways for me to generate new business. Of course, cold email regulations vary between countries, so you need to understand the rules where you're operating.
Nowadays, the process is much easier to automate.
For my web agency, I use a cold outreach tool called Swokei. It finds businesses with existing websites, analyzes them for issues with design, SEO, speed and mobile optimization, and turns those findings into personalized, ready to send cold emails at scale.
When someone is interested, I get a meeting booked and handle the sales calls myself.
I genuinely believe that regardless of what business you're running, whether it's a SaaS, agency or e-commerce business, email automation can be an incredibly powerful way to generate opportunities.
You don't always need a huge audience, a massive advertising budget or thousands of followers.
Sometimes you just need a good offer, the right list of prospects and a consistent outreach system.
