DEV Community

Cover image for I Built an Anonymous Confession App for Developers – Here's How
Getinfo Toyou
Getinfo Toyou

Posted on

I Built an Anonymous Confession App for Developers – Here's How

#showdev #webdev #javascript #react

Every developer has code they're ashamed of. Bugs they've hidden. Interviews they've bombed. I built an app for all of it.

DevConfessions is a 100% anonymous confession platform for developers. No login, no tracking, no judgment. Just share your truth and move on.

Here's how I built it.

The Problem

Developer communities are fantastic for knowledge sharing, but terrible for vulnerability. We post our wins; we hide our failures.

This creates a toxic dynamic where everyone compares their messy reality to everyone else's curated highlight reel.

I wanted to build something different: a space where developers could be honest without consequences.

Tech Stack Overview 

Frontend: Ionic React 7.6+ with Capacitor
Backend:  PHP + MySQL with PDO
Hosting:  cPanel shared hosting with SSL
Enter fullscreen mode Exit fullscreen mode

Not the sexiest stack, but it works. Here's why I made these choices:

Why Ionic React?

I needed one codebase for web and mobile. React Native would require maintaining separate web and mobile projects. Ionic + Capacitor gave me:

  • Single codebase
  • Native Android (and eventually iOS)
  • Web deployment for free
  • Familiar React patterns

Why PHP?

Controversial choice in 2026, I know. But:

  • Extremely cheap to host (shared hosting works fine)
  • PDO prepared statements prevent SQL injection out of the box
  • Fast enough for this use case
  • I know it well

Sometimes boring technology is the right choice.

Architecture Decisions

Anonymous by Design

Anonymity isn't just "no login." You have to think about:

IP Privacy: Instead of storing raw IPs, I hash them with SHA-256:

$ip_hash = hash('sha256', $ip . $secret_salt);
Enter fullscreen mode Exit fullscreen mode

This allows rate limiting without storing identifying data.

Secret Keys: When you post a confession, you get a unique secret key:

$secret_key = bin2hex(random_bytes(32));
Enter fullscreen mode Exit fullscreen mode

This key powers two features:

  1. Private tracking URL to see your confession's stats
  2. Ability to delete your confession anytime

Trending Algorithm

Confessions are ranked using a simple trending formula:

$trending_score = $upvotes / (($hours_since_posted + 2) ** 1.5);
Enter fullscreen mode Exit fullscreen mode

The + 2 prevents division by zero and gives new posts a fair chance. The exponent 1.5 provides decay over time.

Rate Limiting

Anonymity attracts abuse. I implemented rate limits tracked by IP hash:

  • Posts: 3 per hour
  • Comments: 5 per hour
  • Upvotes: 100 per hour 
$recent_count = $stmt->fetchColumn();
if ($recent_count >= $limit) {
    http_response_code(429);
    echo json_encode(['error' => 'Rate limit exceeded']);
    exit;
}
Enter fullscreen mode Exit fullscreen mode

View Tracking

Views are tracked using Intersection Observer on the frontend, with debounced batch API calls:

const observer = new IntersectionObserver((entries) => {
    entries.forEach(entry => {
        if (entry.isIntersecting) {
            addToViewQueue(entry.target.dataset.confessionId);
        }
    });
}, { threshold: 0.5 });
Enter fullscreen mode Exit fullscreen mode

This prevents hammering the API while ensuring accurate view counts.

Challenges and Solutions

Challenge 1: Spam Prevention Without User Accounts

Anonymous systems attract spam. Without accounts, traditional approaches don't work.

Solution: Multi-layered defense

  • Rate limiting by IP hash
  • Content length limits (min 10 chars, max 2000)
  • Client-side and server-side validation
  • Community moderation via upvotes

Challenge 2: Mobile Performance

Ionic apps can feel sluggish if you're not careful.

Solution:

  • Virtual scrolling for long confession lists
  • Lazy loading images
  • Debounced API calls
  • Minimal bundle size (no excess dependencies)

Challenge 3: Privacy vs. Features

Some features (like user profiles, following, notifications) would require accounts, which breaks anonymity.

Solution: Accept the constraint. The platform does one thing well—anonymous confessions—rather than trying to be everything.

Lessons for Developers

  1. Boring tech is fine. Don't let Stack Overflow shame you into over-engineering.
  2. Privacy is a feature. Design for it from the start, not as an afterthought.
  3. Constraints enable creativity. No accounts meant no feature creep.
  4. Ship early. The platform has rough edges, but real users taught me more than any amount of pre-launch polishing would have.

Try It Out

DevConfessions is live on web and Android:

🔗 Web: https://devconfessions.getinfotoyou.com

📱 Android: Google Play Store

If you've got a shameful code confession, a hidden bug, or a failed interview story-there's a category waiting for you.

And if you've got feedback on the tech stack or architecture, I'm all ears in the comments!

Top comments (0)