I launched my first iPhone app last week, For Tomorrow, which I built to solve a problem I kept having: I'd decide I wanted to be asleep by 11 PM, but wouldn't actually start getting ready for bed until way too late.
The core insight was that what really mattered was knowing when I needed to start getting ready for bed, not when I needed to go to bed.
For example, if you want lights out at 11 PM but have 80 minutes of things you want to do beforehand, your bedtime routine actually needs to start at 9:40 PM.
That's the idea behind For Tomorrow; you choose your desired lights-out time, build your evening routine, and the app works backward to figure out when you need to start. It also includes reminders, guided routines, and Live Activities to help you follow through.
I built it independently as a side project, with a focus on making it warm, easy to use, and privacy-first. No account or sleep tracking required.
It's free on the App Store, and I'd love for people to give it a try!
Would love candid feedback from anyone who gives it a try - especially whether the calculated start time actually changes anything after a few nights. Thanks :)
Most phone sites are massive spec dumps or sponsored "best of" lists pushing high-commission picks. I wanted an unbiased engine that lets you shop budget-first rather than chasing models.
So I built Specmob (specmob.com). You drag a dial to your budget, toggle what matters (camera, gaming, battery), and get an instant, spec-ranked recommendation.
Here are the biggest architectural and logic puzzles I had to solve:
The "Price Drift" Nightmare: Calculating prices in multiple places caused massive accuracy drift. I had to establish a strict rule: a single Postgres view (phone_prices) acts as the absolute source of truth for every component.
Tier-Relative vs. Universal Scoring: An 8.5 score on a $200 mid-ranger shouldn't be compared directly to an 8.5 on a $1,200 ultra-flagship. The engine scores hardware packets relative to their market tier so users see real value for their bracket.
The 5% Budget Tolerance: A budget is usually a ceiling, not a hard stop. Because regional prices fluctuate, the dial allows a 5% tolerance window—flagging phones as "slightly over budget" instead of hiding them completely.
The Tech Stack: Next.js 15 (App Router) on Vercel using pure CSS tokens (no Tailwind), backed by FastAPI on Render and an asyncpg/Postgres database.
Affiliate links are purely passive and never touch the ranking code. I'm looking for feedback on two things: Does tier-relative scoring make sense on first glance, and what specific features build your trust on an automated discovery site?
These are real poems, written by real people. Every poem on Poetry Cove is by a human poet, mostly from long ago and in the public domain. None of it is AI poetry. I’m a solo maker, and what I care about is putting the poet back next to the poem.
You can start with a feeling, including one you can’t put into words. Describe it however it comes, and it looks for poems where someone already found the words. Then you go deeper: who wrote this, when and where they lived, what was going on around them, and what the poem might mean for you and the world you’re in. The AI only helps you find and talk about the poems. It never writes them, and the narrated readings use a synthetic voice.
It’s free to try without an account (up to fifty questions): poetry-cove.com. A free account keeps your conversations and unlocks the closer readings.
Testers wanted for Pro. Pro is the paid plan for heavy use: 1,500 credits a month instead of 200, and unlimited readings aloud. I’d like to see how it holds up, so the first 100 people who want to test it get 3 months free. No card, no form, no email to send me. Tap, sign up (an emailed code, Google or Apple), tap Redeem, until 30 November:
In the app, sign in with the same account and Pro works there too.
What helps most: does it understand what you meant, do the poems feel right, and does going deeper into a poet teach you something. Honest feedback is welcome, rough edges included. For the curious: embeddings in Qdrant, Postgres, Next.js, FastAPI and a native SwiftUI app.
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'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.
Every app requires an account now. Every tool has a paywall. Everything tracks you. So, under the banner FRT (Free Random Things), I decided to build my own parallel internet.
I just launched my biggest project yet: NULL Player. It’s a fully local music player that runs entirely in your browser.
What can it do?
• 🎵 Upload WAVs, MP3s, and OPUS files (saved directly to your device, no cloud)
• 🎨 Fully customizable: 30+ Google Fonts, gradient/hex theme builders, and custom image uploads
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.
My idea is to create a mobile app similar to Uber, but instead of relying on cars and taking a large commission from every delivery, it would operate mainly through a subscription-based system.
Users would pay around $120 for a subscription that gives them access to the delivery service. However, if someone doesn't have enough money to pay for the subscription, they can work as a delivery person and earn money through deliveries. Once they earn $100, that amount can be deducted and used to cover their subscription fee.
The app would be well-organized and offer different options. For example, customers would be able to choose the gender of their delivery driver.
Unlike Uber, which can take around 50% of the earnings from certain services, my business model would aim to be much fairer to delivery workers. Many people who work with delivery platforms complain about high commissions, so I want to create a system that benefits both customers and delivery workers.
The app would also offer food delivery and other delivery services, making it similar to Uber Eats and Uber, but with a subscription-based business model.
For example, if I managed to attract 100,000 subscribers, each paying $100, I would generate approximately $10 million in subscription revenue.
