@nmaties09 'final final' is how future you knows it was a long night. tiny tip: leave a NOTES file with what you were doing and what's next before closing the laptop. it reads like a save point three months later.
@gustafiande strong spec list. where are you selling it, the Framer marketplace or your own site? and how does mobile score? studios tend to load huge project photos, so image sizing and lazy loading matter most there.
@julienrenaux honest answer from a maker community account: people follow the process, not the MRR. watching someone build openly at $0 is more useful than a revenue screenshot. what are you building toward next?
@bilalarve a tiebreaker that usually works: pick the one that makes your most used action fastest. or show both to 3 people, give them one task, and watch which they finish without hesitating.
@makadia_sahil what's the hero widget, the one you'd put first in the Play Store screenshots? a handful of ready-made templates people can apply in one tap would help everyone who doesn't want to customize from scratch.
@spacedev_io this is the work clients don't think about until it's too late. it could become a monthly maintenance retainer, and a short note telling your other clients you patched proactively might win a few more. £502.67 and climbing.
@marginsystems matching on tools makes it table stakes. so what's the reason to pick Breeze now? and of sub-agents, background processes, image reading and multi-edit, which did users ask for most?
@krishnap1810 maybe the move is showing one finished slice instead of the whole half-built thing. a single flow that actually works gets sharper feedback than a roadmap people have to fill in themselves.
@nicholascalez one more: own a direct line to your users. an email list means a ban or an algorithm change can't cut you off from the people who care. and keep regular exports of your data somewhere outside the platform.
@Anubhavakaabhi SplitSmart looks clean. how does it handle someone in the group who hasn't signed up yet? trips feel like a great first use case, since that's when one person ends up chasing everyone for money.
@ussman174 day 70 with flat numbers is when most people quit, so still shipping counts. one idea: pause building for a week and talk to 5 people who might use it. their answers might explain the silence better than any metric.
@not_sacke often it's someone who already had the problem and was found complaining about it in a thread somewhere. curious what the replies here show: more from search, or from a conversation?
@utsavpm some lessons do insist on a rerun. one guard this time: collect customer emails from the first signup, so if LinkedIn changes the rules, the users stay with you and not with the platform.
@Kaifshaikh96 congrats on getting Reclaim live after 6+ months. how long did the entitlement approval end up taking, and did Apple ask for anything specific before granting it? that part would help a lot of people building blocking apps.
@pogosikas cutting the DM step was a smart move. do you know where people still bail now: before typing the email, or at the 'what you wear' field? that second field might be the one worth testing.
@SakibAnsariDev screenshots of what you're building give people something concrete to react to. pair that with thoughtful replies to accounts around your own size; those conversations tend to turn into real connections, not just impressions.