Reddit Community Analysis: r/developersIndia

1. Data Sources & Methodology

• 339 unique posts after deduplication across 4 time periods (all-time, year, month, week), 4 pages each (16 raw JSON files)
• Date collected: April 3, 2026
• Subreddit subscribers: 1,517,660
• Score range: ~1,469 to 7,406
• Median score (dataset): ~2,200 (estimated from ~170th ranked post)
• Top 25 threshold: ~2,934

Cross-subreddit calibration: r/developersIndia peaks at ~7,406, compared to r/india's ~37,554, r/webdev's ~18,701, r/ClaudeAI's ~8,084, and r/macapps' ~2,029. With 1.5M subscribers, this is a large but niche-identity community. A score of 3,000+ is a genuine hit. A score of 2,000 is strong. Below 1,500 is solid year-level performance. The subreddit has lower peak scores than r/india despite being a comparable India-focused community, because the audience is narrower (software professionals only) and memes/rants have been banned since 2023.

2. Subreddit Character

r/developersIndia is the emotional support group, career counselor, and town square for India's 1.5 million software professionals -- a place where developers process the anxiety, absurdity, and occasional triumph of working in the Indian tech industry. It is not a technical forum. It is not a product discovery platform. It is a community where the human behind the code gets to speak.

Product launches and "I Made This" posts are enthusiastically welcomed, but only when they carry a personal narrative. The community celebrates builders who frame their work through struggle -- "I got laid off so I built this" (3,634 score), "Hosted my own cloud storage because Google Drive sucks" (4,132 score). Pure self-promotion without narrative context gets filtered by moderators and ignored by the community.

Humor once dominated but is now banned. Rule 10 explicitly bans memes and rants indefinitely (since July 2023). Pre-ban meme posts like "Unexpected customer" (4,169) and "Hotstar down as their domain got expired" (3,337) sit in the all-time leaderboard as historical artifacts. Current content skews heavily toward career narratives, project showcases, and industry commentary.

The technical level is mid-career to early-career. The audience skews toward 1-5 YOE developers, many from Tier-2/Tier-3 colleges, working at WITCH companies (Wipro, Infosys, TCS, Cognizant, HCL) or early-stage startups. FAANG employees exist but are treated with skepticism ("An Amazonian joined my company and then this happened!" -- 2,627 score, a takedown of MAANG-credentialed incompetence).

Core cultural values, ranked by evidence:

1. Anti-exploitation: Posts exposing toxic work culture, unpaid internships, and employer abuse consistently go viral (Nomora exploitation: 3,960; Manager died from overwork: 2,154; Never trust HR: 2,984)
2. Salary transparency: The community obsessively shares salary progressions, CTC breakdowns, and negotiation stories. LPA figures are the currency of social proof.
3. Meritocratic optimism: "Tier-3 to FAANG" stories are the community's favorite genre. The belief that hard work and skill can overcome institutional disadvantage is core mythology.
4. Anti-gatekeeping: Posts calling out paid referral schemes (1,538), fake experience (2,267), and interview exploitation (2,394) reflect deep frustration with systemic unfairness.
5. Builder identity: "I Made This" projects get genuine engagement when they solve a relatable Indian problem (road accountability app, cab fare comparison, Zomato exploit).

Enforcement mechanisms: 13 explicit rules including mandatory flair usage (Rule 2), no low-quality posts (Rule 3 -- expanded to ban LinkedIn screenshots, gender/age mentions, diversity hiring rants, tech influencer drama), no political discussions (Rule 6), no memes/rants (Rule 10), no meta drama (Rule 11), and no direct job posts (Rule 13 -- use megathreads instead). Self-promotional content has recently updated rules requiring disclosure. The mod team is active, volunteer-driven, and communicates through detailed announcement posts.

How this sub differs from r/india: r/india is a national consciousness forum driven by politics and social commentary. r/developersIndia is narrowly career-focused with an explicit ban on political discussion. The overlap is in "India problems through a tech lens" posts (data breaches, H1B policy, Bangalore infrastructure).

How this sub differs from r/webdev: r/webdev is a craft-identity community for web developers globally. r/developersIndia is a career-identity community for Indian software professionals. Technical discussions are secondary to career narratives here.

3. The All-Time Leaderboard

Median score of full dataset: ~2,200. Top 25 threshold: 2,934. The dataset skews heavily toward career narratives and "I Made This" showcases in the top 25.

4. Content Type Dominance at Scale

Most surprising finding: "I Made This" posts have the highest average score among recurring flairs (~2,600), beating even General posts. This is a community that deeply values builders -- but only when the builder tells a compelling story alongside the demo. The "I Made This" flair has detailed posting guidelines (linked in the wiki) that require context, not just a link.

5. Content Archetypes That Work

Archetype 1: "From Nothing to Something" -- The Tier-3 Triumph Story

Score range: 1,472 - 5,125 Examples:

• "My success story from a failure in school...to a millionaire in the US" (5,125)
• "Guys guys guys... Listen" -- 15k/month to 6 LPA (2,740)
• "After working for 2.8 LPA for 2.9 years finally got 8 LPA" (2,429)
• "My Journey from a Tier 3 College to a 16 LPA off-campus offer" (1,708)
• "A small win. Got 120% hike thanks to this subreddit" (1,726)

The pattern: The protagonist starts from disadvantage (Tier-3 college, low salary, career gap, family financial stress), grinds through adversity, and achieves a milestone that would seem modest elsewhere but is life-changing in the Indian context. The story MUST include specific salary numbers (in LPA), the exact tier of college, and a moment of emotional vulnerability.

Why it matters for distribution: If you are launching a product or tool that helps with career advancement (resume builders, interview prep, skill platforms), framing your own journey through this archetype gives you instant credibility. The community does not trust outsiders selling solutions; it trusts people who have lived the struggle.

Archetype 2: "I Built This Because X Sucks" -- The Frustration-Fueled Builder

Score range: 1,469 - 5,126 Examples:

• "I built real dark mode for my website - your cursor is now a flashlight" (5,126)
• "Hosted my own cloud storage because Google Drive sucksss" (4,132)
• "I wrote a Bash script to skip a Rs50 usage fee" (3,773)
• "I built a website that lets you transfer Spotify playlists to YT Music" (3,305)
• "I built Boeing Flight Detector" (1,750)
• "Built a free app to compare real-time cab fares" (1,469)

The pattern: The post title names a specific frustration, then presents a technical solution. The best-performing posts combine technical ingenuity with relatable Indian frustrations (Google Drive storage limits, hidden app fees, OTT ad annoyance). Videos and screenshots demonstrating the working product dramatically outperform text-only descriptions.

Why it matters for distribution: This is the highest-ceiling archetype for product launches. Frame your product as a personal solution to a widely shared frustration. The title formula is: "I [built/wrote/made] [thing] because [specific problem]." Include a demo video or screenshot. Open-source your code for bonus points.

Archetype 3: "The System is Broken" -- Corporate India Exposé

Score range: 1,559 - 3,960 Examples:

• "Nomora terminated me after 28 days...refused to pay a single rupee" (3,960)
• "just another day at office. Toxic culture at its peak" (3,931)
• "Never trust an HR, No matter what" (2,984)
• "Company terminated me because I didn't complete 9 hours" (1,559)
• "My friend at Microsoft just got laid off--AI's impact feels way more real" (3,028)

The pattern: A first-person account of corporate exploitation, with specific details (company name, timeline, screenshots of communications). Posts that name the company and the individuals involved get significantly more engagement. The community acts as a collective warning system for exploitative employers.

Why it matters for distribution: If your product addresses workplace issues (contract management, salary transparency, employee rights), sharing these stories and positioning your tool as the solution generates organic interest. Do NOT create fake corporate horror stories -- the community is vigilant about astroturfing.

Archetype 4: "The Numbers Don't Lie" -- Salary Progression Reveal

Score range: 1,478 - 3,085 Examples:

• "I negotiated a raise from 44 to 66 LPA" (3,085)
• "Tripled my CTC (Again)! Tips & experience for interviews" (2,463)
• "I am an indie dev, earning 4-5L/mo" (2,916)
• "My Salary For the past 7 years. From 3.5 LPA to 4L per month" (1,943)
• "From Rs.10k a month to Rs.2000 an hour" (2,134)

The pattern: Detailed salary progression with exact CTC numbers at each stage, years of experience, and the specific actions that triggered each jump (switching companies, negotiating, freelancing, remote work). The community craves specific, verifiable compensation data because Indian salary culture is notoriously opaque.

Why it matters for distribution: If you are positioning a career tool, including your own salary progression data (or aggregated data) establishes immediate trust. Salary numbers in titles get clicks.

Archetype 5: "India vs. The World" -- Comparative Industry Commentary

Score range: 1,479 - 3,898 Examples:

• "To My American Friends Who Outsource to India Please Chill" (3,898)
• "Moving to the US from India...India loses because we play a Zero Sum Game" (3,273)
• "Oh man! Our entire team has been replaced by Vietnam developers" (2,853)
• "Interviews in India are insane compared to interviews at EU" (1,906)
• "H1-B Visa Fees Hike - Indian brain drain finally comes to an end?" (2,149)

The pattern: Posts that compare the Indian developer experience to international contexts (US, EU, Vietnam) through specific personal anecdotes. The community has deep anxiety about India's position in the global tech hierarchy and engages intensely with comparative analysis.

Why it matters for distribution: If your product has international reach or positioning, framing it through the India-vs-world lens generates discussion. "Built in India for the world" hits different here than on r/webdev.

Archetype 6: "Wholesome Hacker" -- Creative/Fun Tech Projects

Score range: 1,606 - 3,401 Examples:

• "I built a multiplayer web game with React & Three.js as no one's hired me" (3,401)
• "I built a robot to shoot coffee at my face if I get distracted" (1,915)
• "I wrote a script that gives me a fake phone call to escape boring situations" (1,891)
• "My boss spams WhatsApp messages, so I built an LLM-based solution" (1,606)
• "Created a Leetcode solver which is completely hidden" (2,001)

The pattern: A fun, slightly absurd technical project that demonstrates skill while making people laugh. The best ones combine genuine technical depth with an immediately relatable use case. Video demonstrations are essentially required for this archetype.

Why it matters for distribution: This is the best archetype for building personal brand before a product launch. Ship 2-3 fun side projects, establish yourself as a creative builder, then launch your real product to an audience that already trusts you.

6. Format Analysis

What Format to Use For What

• Project launches / "I Made This": VIDEO is king. 7 of the top 10 "I Made This" posts are videos. Screen recordings showing the working product with clean UI get the highest engagement. If video is not possible, a clean screenshot (IMAGE) works but has a lower ceiling.
• Career stories / Personal Wins: TEXT dominates. These are narrative posts that require the reader to absorb a journey. The best ones are 300-800 words with clear structure (numbered timeline, specific salary figures, TL;DR).
• Industry news / workplace exposés: IMAGE (screenshot of email, chat, or news article) + TEXT commentary in the post body. The visual evidence is critical for credibility.
• Discussions / Questions: TEXT only. Keep it under 200 words. A single pointed question generates more discussion than a wall of text.

What Makes a Good Demo Video

Based on top-performing video posts:

1. Show the working product immediately -- no 30-second intro. The cursor-flashlight dark mode post opens with the effect in action.
2. Keep it under 60 seconds for simple projects, under 2 minutes for complex ones.
3. Screen recordings only -- no talking head, no webcam. The code output and UI ARE the content.
4. Mobile-friendly framing -- most Indian Reddit users browse on phones. Ensure text and UI elements are readable on small screens.
5. Include a "wow moment" in the first 5 seconds -- the moment where the viewer thinks "wait, that's cool."

7. Flair/Category Strategy

Raw Performance Ranking (by average score)

1. Meme (~2,900 avg) -- Banned since 2023. Historical artifacts only.
2. Company Review (~3,960 avg) -- Small sample but explosive when used for corporate exposés.
3. I Made This (~2,600 avg) -- Highest-ceiling flair for product builders.
4. News (~2,800 avg) -- India-specific tech/policy news with dev angle.
5. Work-Life Balance (~2,500 avg) -- WLB horror stories resonate deeply.
6. General (~2,350 avg) -- Catch-all; high volume, moderate ceiling.
7. Personal Win (~2,250 avg) -- Salary/career milestones.
8. Interviews (~2,150 avg) -- Interview experiences, tips, horror stories.

Distribution Utility Ranking

1. I Made This -- The ONLY flair appropriate for product launches. Strict guidelines exist (link in wiki). Must include context, not just a link.
2. General -- Best for discussion-starter posts that indirectly mention your product ("I noticed X problem, here's what I found works...").
3. Personal Win -- Ideal for "I built X and it reached Y milestone" posts.
4. Help -- Useful for seeding questions that your product answers. High comment engagement.
5. Tips -- Good for educational content that positions you as an expert in your product's domain.

Flair Rules (from Rule 2)

Extended flair rules are linked in the wiki. Using the wrong flair results in post removal without warning. When in doubt, use "General."

Pricing Model Hierarchy (Community Preference)

1. Free / Open Source -- Highest engagement. Open-sourcing code is the single best trust signal. ("I built Boeing Flight Detector -- code is open sourced here" -- 1,750)
2. Freemium with generous free tier -- Tolerated if the free tier is genuinely useful.
3. One-time payment -- Not commonly discussed, but not hostile.
4. Subscription -- Low hostility compared to r/macapps. Indian developers are pragmatic about pricing.
5. Paid with no free option -- Will get asked "why isn't this free?" but not aggressively downvoted.

8. Title Engineering

Top 10 Title Deconstruction

1. "Is this problem solveable with a week/end hackathon?" (7,406) -- Crowdsourcing format. Invites participation. The question mark is doing heavy lifting.
2. "I built real dark mode for my website - your cursor is now a flashlight" (5,126) -- Built + specific novelty. The dash separates the claim from the payoff.
3. "My success story from a failure in school...to a millionaire in the US" (5,125) -- Contrast arc. "Failure" to "millionaire" creates irresistible narrative tension.
4. "I learned interview skills from a candidate today!" (4,631) -- Role reversal. The interviewer learning FROM the candidate is unexpected.
5. "Hosted my own cloud storage because google drive sucksss" (4,132) -- Frustration + action. The extra s's convey genuine emotion.
6. "India's biggest data breach" (3,986) -- Superlative + national stakes.
7. "Nomora...terminated me after 28 days, refused to pay a single rupee" (3,960) -- Company name + specific injustice + "single rupee" creates outrage.
8. "just another day at office. Toxic culture at its peak" (3,931) -- Casual, world-weary tone. Lowercase signals authenticity.
9. "To My American Friends Who Outsource to India Please Chill" (3,898) -- Direct address to outsiders. India-vs-world framing.
10. "I wrote a Bash script to skip a ~Rs50 usage fee" (3,773) -- Specific technical action + specific tiny amount = relatable hacker energy.

Title Formulas That Work

The Struggle-to-Win Arc: "[Starting point] to [ending point]" with specific numbers

• "From Rs.10k a month to Rs.2000 an hour" (2,134)
• "After working for 2.8 LPA for 2.9 years finally got 8 LPA" (2,429)
• "From 430 applications to a Senior Data Scientist role (50L CTC)" (1,512)

The Frustration Builder: "I [built/made] [thing] because [specific frustration]"

• "Hosted my own cloud storage because google drive sucksss" (4,132)
• "I wrote a Bash script to skip a ~Rs50 usage fee" (3,773)
• "Tired of seeing garbage everywhere, so I made a website to report waste" (2,236)

The Corporate Exposé: "[Company name] [specific action] [specific consequence]"

• "Nomora terminated me after 28 days, refused to pay a single rupee" (3,960)
• "I resigned so HR told me come to office daily" (3,096)
• "Top performer SDE in Flipkart got laid off citing performance issue" (1,665)

The Humble Flex: "[Achievement] + qualifier"

• "Guys guys guys... Listen" (2,740) -- The deliberately vague title builds curiosity
• "A small win. Got 120% hike thanks to this subreddit" (1,726)
• "Finally got placed!" (2,265)

Title Anti-Patterns

• No marketing-speak: Zero posts in the top 100 use words like "revolutionary," "game-changing," or "disruptive." The community interprets these as startup hustle-culture signaling.
• No star/download counts: Unlike r/macapps, this community does not care about "10,000 downloads" or "500 GitHub stars." Lead with the problem solved, not traction metrics.
• No AI-slop titles: Titles that read like ChatGPT output ("Unlock Your Potential with...") get instantly detected and downvoted. The community has an explicit cultural allergy to AI-generated content since the Apna College open-source scandal.
• No clickbait without payoff: "You won't believe what happened" style titles are absent. The community rewards specificity: name the company, state the salary, describe the project.

9. Engagement Patterns

If your goal is VISIBILITY: Use the "Frustration Builder" archetype with a VIDEO demo under "I Made This" flair. High upvotes, moderate comments, broad reach.

If your goal is RELATIONSHIPS and discussion: Post under "Help" or "General" flair with a genuine question about a problem your product solves. Ask for feedback, not downloads. The C/U ratio on help posts (0.15) is nearly double that of project showcases (0.08).

Highest-Discussion Topics (regardless of score)

1. Salary negotiations and CTC breakdowns -- Every salary post generates 200+ comments with people sharing their own numbers
2. AI replacing developers -- Claude/GPT anxiety is the hottest topic of 2025-2026 (429 comments on "Claude is dangerously good")
3. Interview horror stories -- 300+ comments when candidates share ridiculous interview experiences
4. Work-life balance debates -- 450+ comments on overwork culture posts
5. WITCH vs. product company dynamics -- The WITCH-to-product-company pipeline is a recurring saga

10. What Gets Downvoted

Ratio Tiers

Anti-Patterns

1. "The Humble Braggart": Posts that claim modesty while showcasing extreme privilege. "My salary for 7 years: 3.5 LPA to 4L per month" (0.91 ratio) -- the community detected humblebragging and pushed back. Posts that own their success honestly (like the 66 LPA negotiation at 0.98) do better than those that pretend to be modest.

2. "The America Dreamer": Posts praising the US while dismissing India generate friction. "Don't come to US if you are born in India" (0.92) and "To My American Friends" (0.92) both generated significant pushback. The community is ambivalent about the US dream.

3. "The Interview Gatekeeper": Interviewers posting about how bad candidates are today. "Took more than 450 interviews for a single vacancy. No one got selected" (0.88) and "I have taken 100+ SDE interviews" (0.93) both drew criticism for perceived arrogance and unrealistic standards.

4. "The AI Doomer": Posts predicting developer extinction from AI get engagement but also pushback. "Claude is dangerously good, feeling irrelevant" (0.96) survived because it was framed as vulnerability, not proclamation.

5. "The Outsider Praising India": "Indian developers are awesome coworkers" (0.91) from an American colleague was perceived as patronizing by a significant minority.

6. "The Reservation/Gender Debate": Rule 3 explicitly bans posts mentioning gender and age unnecessarily, and diversity hiring rants. Posts that skirt these rules get reported and removed.

7. "The Cheating Apologist": "Offline interviews are the need of the hour" (0.89) started as a complaint about cheating but the OP's edit ("I realized everyone cheats") alienated the community.

11. The Distribution Playbook

Phase 1: Pre-Launch (2-4 weeks before)

1. Lurk and absorb the vocabulary: This community has specific lingo -- LPA (lakhs per annum), CTC (cost to company), WITCH (Wipro/Infosys/TCS/Cognizant/HCL), Tier-1/2/3 (college ranking), YOE (years of experience), NP (notice period). Using this naturally signals insider status.
2. Participate in Help and Career threads: Answer questions about your domain expertise. Offer genuine advice. Build comment karma. The community notices helpful regulars.
3. Share a "fun side project" post (Archetype 6): Ship something small, creative, and tangential to your main product. This establishes you as a builder, not a marketer.
4. Read the extended flair rules (linked in wiki) and the "I Made This" posting guidelines before crafting your launch post.

Phase 2: Launch Day

1. Use the "I Made This" flair for product launches. No exceptions.
2. Title formula: "I [built/made] [product name] [because/to solve] [specific Indian frustration]". Include a concrete detail. "I built a tool to compare cab fares across Uber, Ola, Rapido" is better than "I built a price comparison app."
3. Format: VIDEO demo (30-90 seconds) or IMAGE (clean screenshot). Never text-only for a product launch.
4. Post body: Personal story first (why you built this, what frustrated you), then features. Include: tech stack, link, and whether it is free/open-source. Explicitly invite feedback.
5. Timing: Post between 9 AM - 12 PM IST (when Indian developers are on their morning commute/coffee break). The dataset's top posts cluster in this window.

Phase 3: First 24-48 Hours

1. Reply to EVERY comment within the first 4 hours. This community values responsiveness.
2. Handle the "why not use [existing tool]?" question with grace. Acknowledge the alternative, then explain your specific differentiation. Do NOT be defensive.
3. Handle the "is this vibe-coded?" question honestly. The community is deeply suspicious of AI-generated code (Apna College OSS scandal, vibe-coding discourse). If you used AI tools, say so, but demonstrate you understand every line.
4. Handle the "what's the pricing?" question transparently. If it is free, say so prominently. If it is paid, explain your reasoning. If it has a free tier, lead with that.
5. Offer to help commenters directly: "DM me if you want early access" or "Happy to walk you through the setup" generates goodwill.

Community-Specific Comment Strategy

Pre-written reply templates for common questions:

• "Is this AI-generated/vibe-coded?": "I used [specific AI tool] for [specific task like boilerplate/tests], but the core logic and architecture are mine. Here's [link to a specific design decision] I made that an AI wouldn't have gotten right."
• "Why should I use this over [competitor]?": "Great question -- [competitor] is solid for [use case]. I built this specifically for [India-specific need] because [personal frustration]. If [competitor] works for you, use it!"
• "What's your tech stack?": Always answer this in detail. The community respects technical specificity. Include framework versions, hosting provider, and cost.
• "Are you hiring?": If yes, share details. If no, still engage: "Not yet, but DM me and I'll keep you in mind." The community has many job-seekers.
• "Can you open-source this?": If possible, say yes and provide a timeline. If not, explain honestly (business model dependency). Never say "maybe later" without a plan.

Stealth Distribution Tactics

1. Answer "Help" posts with genuine advice that naturally references your product as one of several options.
2. Participate in "what tools do you use?" discussions (they appear regularly under General flair). Mention your tool alongside established ones.
3. Comment on related "I Made This" posts with genuine praise and a subtle mention: "Cool project! I'm building something adjacent -- [brief description]."
4. Cross-pollinate with Discord: The subreddit has an active Discord server (669,880+ members). Engage there first for warmer reception on Reddit.

Score-Tier Calibration

• "I Made This" product launches: Realistic ceiling is 1,500-3,500. Posts above 3,000 all have either a viral demo video or a deeply personal story. Do NOT expect 5,000+.
• Personal Win / Career stories: Ceiling is 2,000-3,000 unless your story is extraordinary (millionaire from Tier-3, 10x salary growth).
• Industry commentary: Ceiling is 2,000-3,500. Requires a specific, personal angle.
• News posts: Highly variable. India-specific tech news (data breaches, policy changes, layoffs) can hit 3,000+.

Post-Publication Measurement

12. Applying This to Any Project

Quick-Reference Checklist

• Title includes a specific frustration or achievement, not marketing-speak
• "I Made This" flair selected (for product launches)
• Post body leads with personal story (WHY you built this)
• Demo video or clean screenshot included
• Tech stack mentioned explicitly
• Pricing model stated clearly (free / open-source / paid)
• Link to product and source code (if applicable) included
• You have 2+ weeks of genuine comment history on this subreddit
• You are prepared to respond to every comment for 4+ hours
• You are NOT posting on a weekend (lower engagement)
• Title uses plain, authentic language (no ChatGPT-style polish)
• You have read the extended flair rules and "I Made This" guidelines

Scenario-Based Launch Guides

If your product is free / open-source

Optimal launch formula: "I [built] [product] because [Indian-specific frustration] -- it's free and open source" + VIDEO demo + GitHub link. Key risk: Being perceived as vibe-coded or AI-slop. Include a paragraph about a specific technical challenge you solved manually. Reference a PR or commit that shows real engineering work. Example to emulate: "I built a website that lets you transfer Spotify playlists to YT Music" (3,305) -- free tool, specific problem, clean demo, link included.

If your product uses one-time / lifetime pricing

Optimal launch formula: Lead with the free tier or trial. Mention pricing casually in the post body, not the title. Frame the paid tier as "if you want to support the project." Key risk: Minimal. Indian developers respect earning money from craft. Just don't lead with the price. Example to emulate: The indie game dev earning 4-5L/month (2,916) -- led with the journey, mentioned monetization naturally.

If your product uses subscription pricing

Optimal launch formula: Frame the subscription as a necessity of ongoing costs (server, API fees). Be explicit about what the free tier includes. Offer a community discount. Key risk: Lower than on r/macapps, but the community will ask "why subscription?" Prepare a transparent answer about operating costs. Example to emulate: No strong subscription success stories in the dataset. This is a gap -- be the first to frame it authentically.

If your product was built with AI

Optimal launch formula: Be transparent: "I used Cursor/Claude for [specific parts], but [specific design decisions] required human judgment." Include a story about where AI failed and you had to step in. Key risk: HIGH. The community is in active crisis about AI replacing developers (429 comments on "Claude is dangerously good"). Being perceived as proof that AI replaces human work is community-hostile. Frame AI as a tool in your process, not the builder. Example to emulate: The indie game dev who mentioned using "Cursor to build most of them" (2,916) survived because he had 13 years of indie dev credibility before mentioning AI.

Cross-Posting Guidance

Based on existing analyses of related subreddits:

• On r/developersIndia: Frame as "I'm an Indian dev who built this to solve [Indian problem]." Lead with personal story, salary context, and college tier. This community wants to know WHO you are.
• On r/webdev: Frame as a technical showcase. Lead with tech stack, architecture decisions, and code quality. Remove Indian salary context. This community wants to know WHAT you built.
• On r/india: Frame as "Technology solving an India problem." Lead with the social impact (corruption transparency, civic utility, consumer protection). This community wants to know WHY it matters for India.
• On r/SideProject: Frame as a builder journey with metrics (users, revenue, tech decisions). This community wants to know HOW it is growing.
• On r/macapps (if applicable): Frame as a polished Mac-native tool. Lead with screenshots and feature comparisons. Remove personal narrative. This community wants to know HOW it works on Mac.