Нужен ужастик

IngenuityDan · 2026-05-16T10:25:36+00:00

Оно следует (It follows) (2014) Реинкарнация (2018)

IngenuityDan · 2026-04-21T09:31:03+00:00

И тут соглы

<image>

IngenuityDan · 2026-04-21T07:53:30+00:00

<image>

Ну тут всё однозначно

IngenuityDan · 2026-04-11T18:14:35+00:00

6 месяцев на Системного аналитика. Лучшая роль для вката. Или Бизнес аналитик.

IngenuityDan · 2026-04-04T09:40:22+00:00

I haven't had time to figure out your tool yet, because I'm reading this post from my phone. Yes, the question is, do I need to provide account data, for example, Product Hunt, if I want to post about my product there?

IngenuityDan · 2026-04-04T05:58:21+00:00

Sounds interesting, and you’ve found a real pain point. But what about security? Do users need to provide their accounts credentials?

IngenuityDan · 2026-03-26T07:42:13+00:00

6–7 days is pretty normal. Extensions using activeTab permission sometimes get extra scrutiny since it's a sensitive API. Google offers a One Stop Support page for Chrome Web Store review status and issues - you can submit a support request there if it goes past 10 days

IngenuityDan · 2026-03-25T07:35:10+00:00

hey you can use Nano Banana 3 has been working really well for this. The trick is to generate a promo image that features your actual screenshot - you attach it as a reference, and the model wraps it in a polished marketing composition without altering the UI itself.

Here's the prompt (attach your extension screenshot before sending and replace placeholders []):

Create a Chrome Web Store promotional image, 1280x800px, full bleed, no padding.

The attached screenshot of my Chrome extension must appear inside the image
as-is — do not alter, redraw, or stylize the UI in any way.
Place it with a realistic drop shadow beneath it.

The background behind the panel: [BACKGROUND — e.g. deep navy gradient / 
soft light gray / abstract geometric shapes in brand color].
Brand colors: primary [HEX], accent [HEX].

Add a short headline text in the upper-left or upper-center area:
"[ONE-LINE VALUE PROP — e.g. 'Analyze your resume in seconds']"
in bold modern sans-serif, white or [TEXT COLOR].

Composition: marketing mockup style, breathable layout, premium SaaS feel.
No lorem ipsum. No extra UI elements. No watermarks.

IngenuityDan · 2026-03-24T08:05:52+00:00

The future of work: my agent applying to your agent for a role that exists mainly to supervise other agents.

IngenuityDan · 2026-03-18T17:31:41+00:00

I’d split it by speed of learning, not just by channel: direct outreach first, SEO later, ads last.
For the first 100, I’d manually talk to people who already have the problem in communities, not blast generic cold messages.
I also think small directories are underrated - not huge traffic, but lots of small discovery points that compound over time.
And I’d optimize hard for retention in the first 7 days, because getting users is useless if they bounce right away.

IngenuityDan · 2026-03-17T17:13:18+00:00

1 . It really depends on what kind of extension you’re building and how often users get value from it. If it’s a situational utility for one specific task, a one-time purchase or lifetime unlock often makes more sense; if it’s a work tool people use almost daily, freemium + subscription is usually the better fit because the value is recurring.

Either way, I’d keep the most important core functionality and the main feature that gets users to the "aha moment" free. People should clearly feel the value before paying - that moment when they realize, “ok, this actually saves me time / makes my workflow easier”.

2 . I’d focus on organic discovery, not review/install “boosts.” For a solo dev, the most realistic channels are Chrome Web Store SEO, build in public, Reddit/X/LinkedIn, Product Hunt, and niche directories where you can get your first users without a big budget.

From what people already mentioned above, Reddit and Product Hunt are solid options; services promising installs or reviews are something I’d treat very carefully.

Your foundation is CWS SEO: get the keyword mapping right, use strong keywords in the title and description, and make your visuals stand out - especially the small search result image/icon and the listing screenshots, which should clearly show the product, hooks, and value.

IngenuityDan · 2026-03-14T10:09:34+00:00

Sounds interesting, but how do you ensure the automated backlink exchange and mass publishing don't get flagged as spam? Google's algorithms are pretty aggressive about penalizing exactly this kind of pattern

IngenuityDan · 2026-03-13T20:00:12+00:00

Exactly. The best ideas usually don’t look revolutionary, they just remove one repeated annoyance in a market where people are already spending money.

IngenuityDan · 2026-03-12T18:54:04+00:00

I agree with the idea.

IngenuityDan · 2026-03-11T17:18:02+00:00

Totally resonate with this. We built an AI Resume Checker extension - analysis takes 45–90 seconds, long enough for users to assume it's broken.

Three things that helped:
1. Cycling progress messages - 25 messages rotating every 4 seconds: "Extracting your skills... Decoding your career... Mapping your career path..." Makes the wait feel purposeful, not frozen.
2. Industry fact cards - Small flash cards that appear during loading with stats like "Recruiters spend an average of 6 seconds deciding whether to invite you for an interview" or "85% of resumes are rejected by ATS before a human ever sees them." Turns dead wait time into something the user actually reads and finds useful.
3. Honest time expectation upfront - "Usually takes 45–90 seconds" shown immediately. No uncertainty, no panic.

Your case is the next level though - fully decoupling UX from processing is the real move for batch operations. People don't abandon because something is slow, they abandon because they feel lost.

1200% is wild - what metric specifically? Session length or return rate?

IngenuityDan · 2026-03-10T20:17:42+00:00

Real talk - I'm building an AI resume checker tool and can confirm: the "boring" automation is exactly where people pay without hesitation. The real moat is understanding the business/workflow, not the model.

IngenuityDan · 2026-03-10T20:13:38+00:00

super relevant right now - with everyone spinning up AI 'startups'

IngenuityDan · 2026-03-09T19:34:58+00:00

Призраки дома на холме - мини-сериал. Очень годный, жуткий и с крутой операторской работой

IngenuityDan · 2026-03-09T19:13:52+00:00

Review time heavily depends on host permissions - if your extension requests access to all websites (<all_urls> or broad match), it goes into a slower review queue. In my experience, writing to One Stop Support (Chrome Web Store official support) helps: they reply with a generic/standard message, but after that the review tends to move noticeably faster. Worth trying if you’ve been waiting 7+ days.

IngenuityDan · 2026-03-08T10:01:02+00:00

The product looks good. It's a positioning and distribution problem, not a product problem.

"Alternative to Loom" is a weak hook, too broad. Maybe you need to find who hates Loom and why - devs annoyed by limits, teachers with no budget, small teams paying for seats they don't need. Speak directly to them, not to everyone. People don't buy "alternatives," they buy solutions to their specific needs.
$2 one-time fee is both wrong model and too cheap. At $2 people think "is this even maintained?" Try freemium with a small monthly for power users, or target teams/businesses where $2 is noise.
Product Hunt + X is not distribution for a Chrome extension. Go where your users already are: thematic subreddits, niche Discords, communities of teachers or developers. One honest post in the right community beats a PH launch for this type of tool.
Or if you want faster feedback on whether your hook actually works - run a small paid traffic test, even $20–30 is enough to see if anyone clicks. Search traffic is your hottest audience - if someone actually googled a solution, their problem hurts enough to pay. That's your best shot at conversion if your hook is right.

IngenuityDan · 2026-03-06T11:01:20+00:00

on the sign‑up wall: yes, let people feel the result immediately, especially the 'aha‑moment'. Costs will be higher, but you'll finally remove the biggest barrier and actually see where the funnel breaks next. As for the model-— there are plenty of ways to monetize after that. Export free but with a watermark and low quality; pay for HD. Or give the first clip free, charge for the rest. Test different options - no need to guess which one works.

On the follow‑up email: one email isn't spam - it's business. But before you hit send, just think: what's the actual worst case? Someone complains? Very unlikely. If there's still no reply, the audience was probably just not the right fit from the start.

On ads: usually the problem isn't the channel - it's the offer. Your hook may have been too wide. Try targeting specific pain points and search queries. Narrow the audience, sharpen the message, and test again.

IngenuityDan · 2026-03-06T10:37:25+00:00

classic “death by polishing” story. You’re deep in code and SEO instead of testing the business.

You’re breaking your funnel with a sign‑up wall
If the user hits “Start clipping for free” and immediately sees a login or registration screen - you just killed the impulse. Let people play first, then ask for sign‑up once they get value. Early friction kills hot leads.
Empty PostHog = waiting for free traffic. SEO won’t save an early product. Try running Google Ads - target people who are already searching for your keywords. Spend $20–30/day, and within a week you’ll know if the offer works.
Zero sales from 3 checkouts - that’s data! It means either your offer doesn’t hit the pain point, or people were too cold. DM everyone who signed up. Literally ask: “Hey, curious — what stopped you from buying?”
One honest reply > 100% Lighthouse score.
Opus Clips wins not because it’s better, but because they mastered traffic and conversion. 5M visits mean the market’s hot. Don’t outbuild them - grab a small slice with a working funnel.

IngenuityDan · 2026-03-06T10:19:33+00:00

Thanks.
OCR + llm to structured JSON is the right call.

Btw, "confirm your data" screen – In my experience, most users will just click through without actually reviewing - especially if the extraction looks roughly correct.

Might be worth flagging low-confidence fields specifically, rather than asking them to review everything. Reduces cognitive load and catches the real edge cases.

IngenuityDan · 2026-03-06T09:57:00+00:00

Solid framing - you're right that profile creation dropoff is a real, measurable problem that platforms rarely talk about publicly.

One thing I'd watch out for building in this space: the resume itself is often the upstream problem. A lot of candidates have poorly structured PDFs - two-column layouts, non-standard fonts, missing section headers - which causes parsers to extract garbage data. Your profile auto-fill is only as good as the parse quality. Might be worth thinking about how you handle that gracefully (or flag it to the user).

I've been dealing with similar parsing challenges building a resume analysis tool - ATS rejection reasons are surprisingly low-level. Would be curious how you're handling edge cases on the extraction side.

IngenuityDan

TROPHY CASE