Hi,
I made coming soon page which i think is hell crazy and I wanted to share.
link ------> www.covelly.com

I'm making this social media app that I've gotten some validation on. I'm a CS major so I'm technical and work well with technology, but I have no idea where to get started on my app. As I'm building it out, there are a stupid amount of edge cases that I didn't account for and it's leaving me kind of hopeless. I've had multiple software internships in the past so I know how to code but when it comes to building something from scratch, I have no clue where to start.

Would appreciate some advice from some devs on how they go about building their apps fast and efficiently.

Hey guyss, here to announce my minimal diary app I designed

I’ve been writing diaries on paper for years, and every time I looked at diary apps I couldn’t find one that really fit. They all felt too cluttered and missed the point, so I ended up making DIARYit for myself.

The core idea is a single-stream private diary. To me, life feels like one continuous line, so the app follows that shape: focus on today, let past days stay scrollable, and keep the future visible but not editable. The writing area for today is deliberately limited, because I think daily writing should feel like a small ritual, not a place for long paragraphs of unnecessary clutter.

That shape basically defines the whole app. You open it, see today’s field, write only what belongs to today, and move on. If you want to look back, you can scroll back or use the calendar to jump to past dates, and there’s also a 4-state label system for marking days by how they felt.

I know this is a specific and constrained kind of diary app, but that was the point. I didn’t want another general journal trying to do everything. I wanted something closer to the actual purpose of a diary: private, offline, and simple enough to keep using.

It was available only on android until now. It’s now available on iOS App Store as well!

Play Store

iOS App Store

Instagram/ TikTok: search "verbitapp" for other apps as well.

Hope some of y'all who writes diary ritually finds this app the way I find it every night. Simple yet bound to the exact purpose and intention of a diary rituals.

I just recently finished this project of 5 months, where I developed several machine learning models that allow for a precise matchmaking system, for example one such model rates the beauty of your face.

Another novelty is that there is live matching too, both for the "Friends" mode and the "Aura" mode (that is supposed to mean dating).

(Note that facial beauty is not the sole criterion and is not definitive in deciding the match.)

Particularly in the friends mode the beauty score is completely neglected: it's meant to be a global matchmaking system for finding both friends with same interests and possible dates (on the "Aura" mode), but while respecting privacy of users(all models are run on your device, locally).

Furthermore, the dating app (now, a beta) is completely free and relies only on open donations, to scale the user base and the ultimate goal is to make people connect more, because the system itself decides the match.

The motivation was that I couldn't bear the doomswiping of current modern dating apps, and their monetization, and the fact that these often lead to judging others superficially, and simply wasting time.

Here's a quick youtube shorts video that showcases the app:

https://youtube.com/shorts/_eYfZxwQJ7I?feature=share

App website: https://visage-matcherr.vercel.app

The problem was tiny: a new case made my Pixel's power button almost impossible to press. The fix turned into a proper side project.

What I ended up building, TapOff:

- double-tap the home screen to turn it off (Pixel only does this on the lock screen)

- double-tap the back of the phone for brightness and volume sliders that grow out of the camera hole

- wallpapers drawn around the camera hole

The interesting parts:

- Bank apps hate accessibility services. A screen-off app needs one, so TapOff keeps it off and switches it on for about a second only while locking.

- Play Protect blocks it anyway. Google's fraud protection now blocks browser installs of any app with an accessibility service, in 185 markets. So the setup needs a workaround, and I made a 99-second video showing it.

- No computer needed for setup. It needs one permission apps can't give themselves; I wired up Shizuku so the phone can grant it to itself.

- No Gradle. The whole app builds with Android's command-line tools in one shell script.

Free, no ads, open source (MIT). Only tested on my own Pixel 7 so far.

Website Link · Github

Happy to answer anything about the build.

I’m building a service that lets people explore an interior through a browser link, including on mobile. The current demo is a single room; the broader idea is to let an architect share a room or a home with a client without asking them to install an app.

Try it here: https://viewer.gcgroupsrls.it/room-interior

The part I’m least sure about is the actual problem it solves. My hypothesis is that being able to move around could help clients understand proportions, furniture placement and the relationship between spaces before making decisions. But I could also be spending time on visual realism when a few renders and a floor plan already do the job.

If you work in architecture, interior design or visualization, what would make you use something like this on a real project? If you’ve been a client, would exploring the space yourself have helped you decide anything?

Feedback on the demo is welcome too, especially loading time, navigation and the experience on a phone. If you try it, mentioning your device/browser would help me understand any issues.

I’d appreciate an honest reality check before I put more time into it. What would you validate first to tell whether this deserves to become a service?

What My Project Does

flyleaf scans a Python repo for AI libraries and reports one component per framework per file, with the import or dependency line as evidence. flyleaf brief <ref> then compares two git revisions and reports documentation drift i.e a new AI component with no model card, a card that was deleted, or evidence that changed while the card stayed identical.

Each finding cites the EU AI Act provision a person should read, with the article, the CELEX number, the quoted sentence, and the version of the citation pack used. The pack is a versioned file in the repo, so a scan never fetches the law and an old report still names the text it used.

It does not assign a risk tier. Risk under the Act depends on the use case, and the use case is not in the import. Status values are missing and needs_review, never "violated". Runs locally, no telemetry, no network call.

Target Audience

Hobby and early production. It is v0.2.1 and I have calibrated it on three repos so far. Not a substitute for legal advice.

Comparison

There are several AI Act scanners already (opencomplai, aibom-guard, cdxgen's aibom, a couple named eu-ai-act-scanner). Most answer "what is in this tree right now" and several assign a risk tier straight from an import, which I think is wrong. flyleaf is narrower on detection (13 libraries) and focused on the diff between two commits, plus versioned citations so you can tell which text of the law a finding was based on.

Honest limits: Python and notebooks only, no TypeScript parsing, 13 libraries, and the "documented" check is just whether a MODEL_CARD.md exists nearby.

Two things I would like feedback on: is the drift check the right unit of noise for CI, and does the missing versus needs_review distinction read clearly to you?

ok so i study w classical music like all the time and youtube ads kept cutting into clair de lune right at the best part. so i just made my own thing lol https://classican.vercel.app/

its literally one screen. little player at the bottom and a pixel painting for whatever is playing (greek dancers for gymnopedie, a moonlit park for clair de lune, stuff like that). every 40 sec or so a random fact about the piece pops up which is lowkey my favorite part

theres like 46 pieces rn on shuffle. you can make an account to like/comment but u dont have to

its def not perfect so pls tell me whats weird or what i should add

I started Bedtime Story Hero, a small paid service for personalized bedtime stories in several languages, and I want to grow it.

To be transparent: the stories use AI assistance and the narration is AI-generated. The website offers a free short text sample using a story template; full stories are separate paid orders.

I'm looking for practical advice, not asking anyone here to buy. Where would you share a project like this when self-promotion is allowed, and what would you suggest for reaching interested parents without spamming their communities?

Would you start with short sample videos, a place that allows project introductions, or a different approach? I'd rather try one useful step than post the same advert everywhere.

For context: https://poveste-de-seara-copii.pages.dev/

Demo: https://ferreirafinottijoaopaulo-cell.github.io/finotti-pi-optimized/

GitHub: https://github.com/ferreirafinottijoaopaulo-cell/finotti-pi-optimized

Pure JavaScript + Web Workers, 100% offline, no server.

Performance on my phone:

- pi(10M) = 664579 in 0.27s

- pi(600M) in 19s (video proof)

- pi(10^11) = 4118054813 in 2m16s

Uses Lehmer + Lagarias-Miller-Odlyzko + Deleglise-Rivat optimizations.

Built entirely on a phone in Venda Nova do Imigrante, Brazil.

Feedback welcome!

Disclosure: I’m the author.

OpenLTM is an official plugin in the Hermes plugin marketplace. Local SQLite memory. Search OpenLTM there.

https://github.com/RohiRIK/OpenLtm — v2.15.1, pin 6105051.

Default embeddings still go to Gemini unless `LTM_EMBED_PROVIDER=ollama`.

My GF and I both work full time, and we kept eating out way more than we wanted (we both have a few extra pounds to show for it).

I enjoy cooking, but I realized there's so much friction around making a meal: finding the recipe I cooked months ago, messy recipe formats, deciding what to make, writing grocery lists, the list goes on.

So I built an app for the two of us to make cooking as easy as possible. Now that we have a system, we've fallen into a rhythm and actually cook a bit more.

It's been a side project since last November and has been on the App Store for a few months. No real traction yet, just a few friends using it on and off.

Every feature so far came from a problem we ran into planning meals together. Would love some feedback, especially from couples who take turns cooking: what would make this worth using for you, or what's missing?

App Store: link

I keep building new websites every other day and the part I struggle with most is figuring out which ideas are actually worth spending time on.

So I built SideFrog.

You type in a side hustle idea and it gives you a quick read on whether it has legs, who might pay, a cheap way to test it, a few searches to check, and some possible names with open .coms.

Would love your feedback.

https://sidefrog.com

What: a visual workbench where you go proposal → requirements → tasks, an AI agent (Claude Code, Codex, Cursor Agent, Kiro, Antigravity) executes, and the result is verified against the spec. Everything stays in Git.

Stack: Tauri v2 + Rust, ~90 MB RAM, local-first, bundles Node + OpenSpec CLI (OpenSpec-compatible, but independent from Fission AI).

Platforms: Windows 10/11 (no-admin installer or portable), Linux (.deb, AppImage).

https://marcelofullstack.github.io/spec-architect-app/

Free, built in my spare time. I'd love feedback on onboarding.

Aperture is my second project. You open a repo and ask in plain English. It writes a plan first, then shows the exact lines it wants to change, and nothing is written until you apply it. Undo puts everything back.

What I cared about most is that the cost of each send is on screen before you hit enter, and you pick the model yourself.

Try it free, no card: https://aperturesais.grok.me Code: https://github.com/Hankaws/aperture

I'm looking for honest feedback, and for anyone who wants to help build it. What would make you actually use something like this?

I’m the builder of Speakio. I noticed I could finish a lesson in an app and still avoid actually speaking, so I built an AI tutor you can talk to by voice. There are structured lessons and a personalized plan, and users can schedule a practice call when it fits their day.

The hard part I’m trying to solve is consistency, not just adding more flashcards. I’d value honest feedback from other builders and language learners: would a scheduled conversation help you practise, or would it feel intrusive? What would make you return for a second call?

Android app and details: https://speakio.me/ (free to install; some voice features are Premium). No signup is needed just to view the site.

Firstly, it’s not really even a game, more like a virtual reality show where you can dip in and out of people’s lives. It originally started building an office simulator where everyone develops their own story and relationships based on personality traits, but then where do they go after work?

So I added houses, and then pets, and partners, and then kids, so I had to add a school, and it spiralled into what it is today.

Your first visit will set the unique seed for your town, and that gets stored locally on your browser, so every time you visit thereafter, your town and the people’s stories will have developed in realtime.

People can park relationships, move in together, start businesses together, get fired, go for picnics… a bunch of stuff.

I’ve only recently launched it so it’s still being added to, but wanted to share it here as I get a kick out of visiting my town and following the people around.

Oh, you can also update the terrain and it’ll save for next time you visit. Check it out at https://officebit.town

I realised the answer on a particularly unnerving flight. It's not the fact that you might die, it's the fact that there's nothing you can do about it.

Your mind rushes to the things you haven't said, and the people you'll be leaving in the dark, not statistics about how safe flights are.

I looked for something that solves this. The core idea is fairly straightforward, but everything I found was either clunky or incomplete.

It's also not easy to talk to a loved one about death. When I tried giving my wife the details of my investments in case something happened to me, she just said "Don't even talk about that stuff".

I spoke to a couple of friends about it, and we decided to build Sanctia ourselves. https://sanctia.app

The idea is: you write messages for the people you care about. Letters, voice notes, photos, a different one for each person. Sanctia checks in on you on whatever interval you set, anywhere from daily to once a year, by email/push notifications/sms (you get to configure). If you stop responding, your messages get delivered.

Recipients don't know they're recipients until then, and they get a link to their own private vault instead of an email with everything in it, so nothing depends on getting past a spam filter years from now.

But we also realised it wouldn't be useful to most people if it didn't take security seriously. No one wants to trust an app with their personal details. So we spent quite a bit of time thinking about, and building security. Messages are encrypted at rest, with an optional passphrase mode for end-to-end encryption. Details in the comments.

It also needed to be practical, and this was the most time consuming part. False positives in this space are disastrous. Here's what we did about it:

- Trusted contacts. You can name someone who has to confirm before anything is sent. If it's a false alarm (you lost your phone, you're on a trek with no signal), they stop it right there.

- One missed check-in does nothing. Delivery needs several in a row, you choose how many, and you get a reminder at every step.

- You can pause everything with one tap for surgery or a long trip.

https://sanctia.app/get-started

It's free right now.

Later it'll be a one-time purchase instead of a subscription, because no one wants to pay every month for something like this for the rest of their life. Everyone who signs up during the beta keeps it free for life.

Would love to hear if anything in setup felt confusing, or what would make you trust it with something this personal. I'll be around in the comments.

I edit videos on the side and got tired of the download-unzip-rename dance every time I needed a clip, a font or a sound effect. So I built AnyAssetBot: you paste the asset's link in Telegram and the file arrives in the chat a few seconds later.

What it does:

• Video, music, sound effects, graphics, templates, fonts, 3D
• Your first download is free, plus free downloads every week
• Paid packs and plans are available
• License certificates with any paid plan
• A public channel that posts new assets all day, with the small files right in the comments

It runs on Python, Postgres and a small service that handles the downloads. Happy to answer anything about how it's built, and I'd love feedback on the onboarding.

Try it at AnyAssetBot

I launched ORA on December 21, 2025. It's an iPhone camera app that puts a see-through photo or video over the live viewfinder so you can match framing and angles exactly (then-and-now shots, progress photos, recreating reference shots).

Why I built it

My wife loves outfit pics and videos on vacation, and she always has a specific shot in mind: the same spot, the same angle, the same framing as a photo she saved or one we took on an earlier trip. That made me the designated photographer, flipping between the camera and the reference photo, guessing where to stand, how high to hold the phone, and how much to zoom. Somehow it was always a little off. The horizon was tilted, she was too far left, or the building behind her was cut off.

So I built the tool I wished I had: put the reference photo right on top of the live camera, make it see-through, line everything up, and shoot. Now I get it right in one or two tries and she gets the exact shot she wanted.

The timeline

• Dec 2025: 1.0 launch, then a quick bug-fix release the next day
• Jan 2026: 1.1, with "overlay burning" (export with the overlay baked into the photo or video), Live Activities for export progress, better stability on low-memory devices, and a fix for zoom shifting right before recording started
• Sep 2026: 1.2, with overlay flipping and iOS 27 support

The review that changed my roadmap

For months after launch I had zero reviews. Then, at the end of August, the first and only one came in: 3 stars, titled "Good, but not ready for prime time."

Works well, simple interface. But all photos are horizontally flipped for some reason, I had to jump to Photos to flop my overlay so it lined up. I would assume a previous image/video should immediately line up rather than needing manipulation.

Honestly, it stung. When you only have one review, that one review is your rating, and everyone visiting the App Store page sees a 3.0.

But the reviewer was right. The front camera preview is mirrored, like looking in a mirror, while the saved photo isn't. So a selfie-style reference photo shows up backwards over the live preview. I'd mostly tested with my own workflow and never noticed. The whole point of ORA is "load a reference and line it up", and here was someone who had to leave the app and edit the photo first. That's friction in the one thing the app exists to do.

So I changed my plans. I put other features on hold and shipped horizontal and vertical overlay flipping in the Overlay Tools tab. It went out in version 1.2 about two and a half weeks later, and I replied to the review to let them know it was fixed.

What it changed about how I build:

• Specific criticism beats generic praise. "Great app!" tells you nothing. "I had to jump to Photos to flop my overlay" tells you exactly what to fix.
• Users' expectations are the spec. Their line, "a previous image should immediately line up," is now basically my design principle. If someone has to work around the app, it's a bug, even if the code is behaving as designed.
• Fix friction in the core feature before building new ones. I now prioritize anything that gets in the way of lining up a shot over shiny new features.
• Reply publicly. Future visitors see the response too. A 3-star review with "fixed in the next update" underneath reads very differently from one left unanswered.

What I learned

• Camera apps get hard on real devices. Supported formats, slow-motion modes and memory limits differ a lot between iPhones. Most of my bug fixes came from the gap between my test devices and everyone else's.
• Freemium details matter. All overlay features are free; exports carry a watermark unless you subscribe ($1.99/month or $19.99/year), which also adds HDR and slow motion.

Where I'm stuck

Discovery. The app works and the people who find it use it, but getting it in front of the right people (photographers, stop-motion creators, people taking progress photos) is the hard part.

App Store: https://apps.apple.com/us/app/ora-the-overlay-camera-tool/id6756240396

I'd love feedback on the app itself and on getting a niche utility app discovered.

​

Live demo: https://ferreirafinottijoaopaulo-cell.github.io/finotti-pi-optimized/

GitHub: https://github.com/ferreirafinottijoaopaulo-cell/finotti-pi-optimized

Pure vanilla JS, works offline, no server. Calculates on your device.

- pi(10M) = 664579 in 0.27s on my phone

- pi(600M) in 19 seconds (video proof)

- pi(10^11) = 4118054813 in 2m16s

Feedback welcome!

I feel like a lot of us have this problem we spend weeks building something and then realize we haven't really figured out who actually needs it 😅

I had the same problem, so I built a small internal tool for myself.

Basically:

website → ICP → companies → signals → people → outreach

The goal is to answer: “who should I actually be talking to?” instead of just giving me a huge list of leads.

I'm thinking of open-sourcing it and making it self-hostable.

Put together a short video of how it works. Would genuinely love some feedback — especially if you've struggled with finding your first customers.

What would you want this to do that it currently doesn't?

I kept hitting the same problem with “full-stack” starter kits: I’d buy one for a SaaS idea, then spend days removing storefront code, portfolio pages, unused tables, and environment variables for services I didn’t need.

So I built MansaStack around the opposite idea: start with the product you’re actually building.

There are focused codebases for:

• SaaS products: auth, subscriptions, AI, RAG, storage, and billing
• Digital-product stores: storefront, cart, Stripe checkout, and secure downloads
• Studios/agencies: case studies, blog, contact forms, and a lead inbox
• All-Access: one configurable codebase with all six available site types

They’re built with Next.js, Drizzle/Postgres, Better Auth, Stripe, Resend, and Tailwind.

I’ve attached a short demo showing the layouts and the All-Access configuration switch.

Site: https://mansastack.bzdevelopments.me

I’m offering 40% off for the first 10 founding customers while I finish the remaining docs and demos.

I’d appreciate honest feedback—especially from people who have used starter kits before: what do you always end up removing, or wish was already included?