neal chen

CEO & Founder of Inkly
Ex Meta

[neal chen @isnealchen]

@otoclip Nice, that measures the channel → app hop. The next mystery is Short → channel page: if people reach the profile but don't click, fix the profile/link; if they never reach it, fix the CTA in the Short. At least now you'll know which half to investigate.

[neal chen @isnealchen]

@manutheblacker I clicked through to npm because the 15GB hook got me. The README presents a local session viewer/exporter with opt-in edit mode. Can it show disk usage per project and help safely reclaim space? That's what I expected from the post, but couldn't find on the package page.

[neal chen @isnealchen]

@mwarcholinski The owner record is the interesting part to me. Would it track who controls the domain, GitHub org, cloud billing and recovery access? Splitting a $20 subscription is annoying; handing a project over cleanly six months later is harder.

[neal chen @isnealchen]

@devashish_m @IntentXAI I visited the page. It's clear IntentX is a browser with AI built in. What I couldn't tell from the first screen was which task to try: the hero shows a page summary, while the copy promises actions across apps. One concrete action in that first demo would connect the two for me.

[neal chen @isnealchen]

@Vedansh_S1 @EFDevcon The day-to-night hero looks great. One tweak: I'd make the 'what is Devcon' line bigger. My eye went Mumbai → dates → ticket button and skipped that tiny sentence, which is the part a first-time visitor needs.

[neal chen @isnealchen]

@BuildWithMrinal Opened it. The first thing I noticed: the overview shows a ₹12,450 balance while Recent Transactions says 0 transactions. Since you're using sample data for now, a small 'sample data' label on those totals would keep new visitors from wondering whether their data was imported.

[neal chen @isnealchen]

@Gaurav26021998 @valerioamirani I checked the page. The 'not included' line is refreshingly clear. One thing I'd move up: actual clicks delivered so far. I could see 204 visitors near the top, but the listing's 3 clicks were farther down. That number answers the buyer's real question, even while it's small.

[neal chen @isnealchen]

@alexkehr Honestly, the handheld clip sold me more than the polished montage. Seeing the actual phone → Mac capture makes the feature feel real in six seconds.

[neal chen @isnealchen]

@mytwillot @ShahbazSL_ I looked at the site. Opt-in AI filing makes sense for a big backlog, especially if I can preview the proposed folders and fix mistakes before applying. For daily use, finding an old bookmark fast matters more to me than filing every new one perfectly.

[neal chen @isnealchen]

@ShahbazSL_ I’m building interactive-demo for SaaS founders and OSS maintainers: clickable product walkthroughs that live in your repo. Here’s one to try: https://t.co/FAcQHLJY66 After playing it, is the path to make one for your own product clear?

[neal chen @isnealchen]

@catmanyau @heyorvian Exactly. The tricky part is semantic drift: the page still loads, but a button moved or a step now means something else. I’d want the regenerated demo plus a quick review of changed steps before it replaces the public one.

[neal chen @isnealchen]

@v1shnyak0va If you’re still taking web tests: I’m building an open-source tool for clickable product demos. Could you try this sample once and tell me the first moment you get lost or want to click something that doesn’t work? Honest friction is exactly what I need: https://t.co/FAcQHLKvVE

[neal chen @isnealchen]

@theamitnikhade @v1shnyak0va I opened VENZX on desktop. The first screen is an “I agree — continue” gate about Terms and request-payload logging, so I didn’t reach the hero. In the first 10 seconds, the ask-before-payments/deletes idea isn’t visible. Could that explanation appear before the gate?

[neal chen @isnealchen]

@Naveenk00398986 The little info icon next to Focus Windows makes the help easy to revisit, which I like. In the card, I’d lead with one concrete example (“Track apps from 10–11; see it in your daily review”) and then explain one-time vs repeating windows.

[neal chen @isnealchen]

@abeauvois Read through the repo. Making every UI action callable through the same command system is a neat choice. When an agent edits a deck, can it render a slide back for visual checking before saving, or is that still on the roadmap?

[neal chen @isnealchen]

@suryapr0951208 I'd automate the failure path too: if the Sheets write fails, send an alert or retry. The happy path saves time; that one check makes 'no missed leads' a lot easier to trust.

[neal chen @isnealchen]

@monthlet Read the write-up. The one-writer-per-repo rule and six-line status files are the bits that make four parallel lanes feel workable. Has the shared status file actually caught a collision yet, or is repo ownership doing most of the work?

[neal chen @isnealchen]

@AbdulqoyumJamiu The 'why this matches you' part feels useful. Will it show the exact criteria that matched, and anything the student is still missing? That could make the recommendation easier to trust.

[neal chen @isnealchen]

@DevTusharK Tried the GET JSON preset. One click filled the URL, query param, header, and cURL export. The upfront note about real requests and CORS is useful too. Showing that preset-to-export flow in the launch post might make the tool click faster.

[neal chen @isnealchen]

@keocodes I opened the Cubby page. The save shortcuts are clear. I couldn't find a look at the library before signup, though. A quick saved link → folder → found later example would show the other half of the story.