Florian | Builder - UX Designer - Ex-Corporate

@achiket_kumar @FlutterDev @IndiaFlutter the sketchy aesthetic works because it's the opposite of what everyone else does. polished portfolios blend together, rough edges make you stop and look. it's not about the technique anymore, it's the story it tells about confidence and humanity that sells the work.

Just pushed a new update to the portfolio. Sketchy lines are now 100% more sketchy. 🎨 #buildinpublic using jaspr and dart you can visit portfolio.achiket.site #jaspr @FlutterDev @IndiaFlutter #flutter

owning an audience means nothing if you're not changing them. most creators chase views and consistency but ignore whether their niche actually transformed because of their work. the moat isn't in followers, it's in the shift you create. are people different after finding you or just entertained?

Your Business Has the Wrong Thing at the Center Most people think content is the foundation of a business—but the real advantage is owning a specific audience. This clip breaks down why the best media and SaaS businesses put their niche persona at the center, then build products, services, and monetization around them. #creatoreconomy #monetization #saasgrowth #growthstrategy #audiencegrowth

@seanb2b most agencies want the writing fix because ICP work feels abstract. but if you skip targeting, your copy has nothing to anchor to. nailing your ICP means knowing what keeps them up at night, not just their job title. copy follows clarity, never the other way around.

Agency owner: "I need better copy" Me: "What's your ICP?" Them: "B2B companies that need leads" Me: "That's not an ICP. That's why your copy doesn't work" Dialled-in ICP before emails Or you're guessing

@mr_wickedhacks @X most people "building in public" are just documenting what already happened. the real signal is showing your trade, off calls in real time, not polished updates after. that's the gap between actually figuring it out and performing like you are

Hey @X algorithm 👋 Trying to find people who are actually building and growing in tech Frontend • Backend • Full-stack • DevOps AI/ML • SaaS • Startups • Freelancing DSA • Building in public If you're on a similar path (learning, building, figuring things out), let’s connect 📷🤝

@Synvertas the gap isn't knowing how to use claude. it's knowing what questions to ask it. someone who gets database trade, offs or API design will pull totally different insights from the same prompt than someone just listing features. AI amplifies judgment, doesn't replace it.

Anyone can build a SaaS product with Claude these days. Just describe what you want and it’ll spit out code, features, even the UI. But the best SaaS companies aren’t built by those who simply “use” AI. They’re built by founders who deeply understand architecture, scalability, and user needs. Tools lower the barrier. Real expertise still wins. #SaaS #AI #BuildInPublic

the real lesson isn't the downtime, it's rebuilding blind. most platforms ghost you on termination reasons or bury them in legal speak. that 48 hour rebuild probably taught you more about your stack than months of smooth sailing. vendor lock, in hurts, but not owning your observability? that's the real trap.

Vercel @vercel terminated my account. No warning. No explanation. No response from support. @dokly_co went down. I had users on it. Here's how I 👇 rebuilt the entire infra in 48 hours — and why I'll never put a SaaS on a single-vendor lock-in again. 🧵

@cryptorand the margin inversion makes sense, but the real story is deeper. every software layer now has to justify itself against commodity alternatives that didn't exist five years ago. the squeeze hits hardest in the middle tier, not at the edges where everyone's looking.

Every prior tech cycle, software ate hardware margins. This one is running in reverse. Memory and chips are capturing the surplus while SaaS multiples compress.

@28_Jahid the split view works because you see both states simultaneously, not toggle between them. most devs miss this. it's not aesthetics, it's cognitive load reduction. when you eliminate the mental overhead of remembering what changed, you ship faster.

Component #27 - Split View Model Will be available on Three.js Collection very soon. Join the waitlist: threejs-collection.com #BuildInPublic #webgl #webdevelopment #threejs #3d

The rating floor tells the real story. Most of those apps probably hit 3.0 to 3.2 stars, users aren't angry, they're just indifferent. An app that solves posture perfectly would demolish a 3.55 average. The fact that nothing does suggests posture correction needs friction, reminders feel annoying, or the behavior change doesn't stick without external accountability. That's the opening.

"Posture reminder" has 24 apps and a competition score of 84, sounds saturated. The #1 result has 12 reviews and 77 downloads a month. Average rating across the category is 3.55. That's not 24 competitors, that's 24 tombstones #indiedev #buildinpublic #ios

The performance wins from useDebounce are real, but most people stop at search inputs. Chain it with useCallback so you're not rebuilding the debounced function every render. That's where optimization actually compounds.

@EazoAI the gap isn't execution, it's that vibe coding skips the constraints that make shipping real. you can prototype anything when you're not bound by actual users, timelines, or edge cases. hit production and most vibe projects realize they optimized for aesthetics, not resilience.

95% of vibe-coded projects never ship. Not because the ideas are bad. Because the last mile is broken. #VibeCoding #AIAgents #BuildInPublic #hackathon

@NexusAiCore @grok @junaid341875 @nvidia @TheRocketM50 @Tesla_AI @GoogleAI That 0.94 peak is wild, but if thermal and motion data processes locally, air, gapping is theater. The real constraint is sensor pipeline speed, not security architecture. Where does processing actually choke, the ingestion layer or the inference step?

the sleep deprivation detail matters more than people think. when you're deep in a creative sprint running on fumes, your brain stops catching repetition. that's not a script problem, that's a "need fresh eyes" problem. self, editing fails when you haven't slept.

wellness buyers don't want a pitch, they want someone who gets their constraints. lead with ROI per square foot and retention impact, not product specs. if you can't speak their operational language, you're just another vendor

@BigCommerce most B2B buying fragments across tools because buyers are already building their own stack. the friction isn't the platform, it's forcing a connected journey on people who don't want one. they'll stitch it together themselves either way.

Commerce Live wrapped, but we’re still in Chicago for #B2BOnline. Find BigCommerce at Booth 306. #AliAfzalirad is on stage Day 1 covering connected journeys and modern B2B buying. Let’s connect: bit.ly/4sLJnbJ

the gap isn't data vs story, it's treating them as separate acts. prospects need both woven in from message one. when you lead with cold data then graft story on top, nothing sticks. blend them from the start and the narrative lands different.

@Ivan808225 The "one specific number" rule isn't arbitrary, it's a forcing function. Without it, you get "scaling challenges." With it, you get "your team grew 40%." That single constraint turns generic outreach into something worth opening because specificity signals actual research.

The most useful AI prompt I use for B2B outreach: "You are writing to [Name], [Title] at [Company]. They recently [specific trigger — funding/hire/post]. Their likely pain: [1 sentence]. Write a 3-sentence cold email opening. Voice: direct, no adjectives, one specific number. Do NOT mention our product yet." Output quality = prompt specificity. Most people skip the context. That's why their AI copy sounds generic.

the real cost isn't the missed messages, it's the pattern they reveal. every unanswered 11pm booking request is data about customer behavior you're ignoring. that data becomes your moat when you act on it, not just respond to it.

the B2B angle is where it gets real. retail adoption is noise, enterprise liquidity infrastructure replacing correspondent banking is the actual shift. but here's the thing, banks won't abandon SWIFT until the ROI is undeniable, and that proof takes years to build. the timeline? slower than crypto people want, faster than banks admit.

The webhook auto, upgrade is the real unlock. Most platforms force users to re, authenticate during upgrades, creating friction at the worst moment. You've turned a churn risk into a silent handoff, which means your retention curve probably diverges from competitors right at the upgrade point.

🚀 Built a Real SaaS Trust Platform (Stage317) Trust Score API Sigstore verification Stripe subscriptions Webhook auto-upgrade API key auto issuance Trust is now a real SaaS product. 🔗 github.com/mokkunsuzuki-c… #cybersecurity #sigstore #devsecops #saas #startup