Usability60Design58Speed57Security76Accessibility80Growth58

Cycling through all six. Tap any point to stop.

Measured on six things

A fair-chance social network for real discovery and thoug...

Speed

57

Lighthouse mobile 70/100 with CLS 0 and TBT 39ms, so layout and main thread are fine — but a 10.3s mobile LCP drags the whole experience. Desktop lands at 84/100, so the problem is mobile-specific weight.

Screenshots

1 / 5

About this app

Crowdwide is a social networking platform built for curious people who want more signal and less noise. Unlike mainstream feeds that reward popularity and volume, Crowdwide prioritizes thoughtful posts, fresh perspectives, and genuine communities around niche interests, crafts, and small obsessions. It offers a calmer, serendipity-driven experience where new voices get a fair chance at discovery. Users can join communities, share work that matters, and connect with people who 'get it' without a popularity contest. The platform is currently small (25 members, 88 posts, 4 communities) and open for early adopters to shape its spaces. Standout features include a discovery-first algorithm based on curiosity rather than engagement bait, community spotlights, and a partner program for like-minded websites and organizations. Crowdwide also has brand ambassadors and a public roadmap, with its code available on GitHub (DeveloperPuneet/Crowdwide), signaling transparency and community involveme...

Key features

  • 1Curiosity-ranked discovery feed designed to surface new voices without engagement-bait popularity contests.
  • 2Public read-only API at /api/v1/posts with cursor pagination, 120 req/min rate limit, and three RSS feeds.
  • 3Community spaces with spotlights, a partner program for aligned sites, and a public roadmap plus GitHub repo.

Target customer profile

Drawn from the product itself, not from a survey.

Demographic

Indie creators and makers (writers, artists, developers) aged 18-35

Pain points

Struggle to get discovered on mainstream platforms without gaming the algorithm or chasing trends

Primary needs

A fair discovery mechanism and a supportive community to share work authentically

Demographic

Community builders and moderators looking for niche spaces

Pain points

Existing platforms prioritize scale and ad revenue over genuine community health and thoughtful discussion

Primary needs

Tools to foster real conversation, manage communities, and highlight member contributions

Demographic

Curious lurkers and enthusiasts (hobbyists, learners) who want signal over noise

Pain points

Overwhelmed by algorithmic feeds full of viral content, ads, and low-value posts

Primary needs

A calmer, serendipitous feed that surfaces interesting people and ideas without popularity contests

Scout Review

Written by AI from measured evidence, scored out of 100.

Crowdwide is an early-stage social network with a clear thesis — discovery by curiosity, not by engagement bait — and a surprisingly mature technical foundation for its size. The security headers are better than most Series A products, the public API is documented with real pagination and rate-limit semantics, and the design system holds together from landing page to app shell. What holds it back is the gap between the pitch and the proof: 25 members, 88 posts, four communities, and social-proof sections where every post has exactly 5 likes and every creator has 5 followers. The mobile LCP of 10.3s is the one hard technical flaw worth fixing this week. Everything else is a matter of the community actually showing up.

Measure by measure

Usability

60

Clear hero CTA hierarchy and a genuinely documented public API with pagination, rate limits and RSS. Weakened by an unlabelled icon rail in-app and small grey body copy that makes longer reads a chore.

Design

58

Coherent dark navy/purple system that carries from landing page into the app shell, with a strong two-line hero and visible product card. Undercut by placeholder-looking '5 likes / 5 followers' social proof and tiny low-contrast eyebrow labels.

Speed

57

Lighthouse mobile 70/100 with CLS 0 and TBT 39ms, so layout and main thread are fine — but a 10.3s mobile LCP drags the whole experience. Desktop lands at 84/100, so the problem is mobile-specific weight.

Security

76

Strong header hygiene — HTTPS enforced, HSTS, CSP, frame protection, secure cookies, 11/13 probe points. Docs are unusually honest about the unauthenticated read-only API and private-community exclusion. Missing SPF and DMARC.

Accessibility

80

Lighthouse a11y audit at 98/100 with only a heading-order failure. No WCAG statement or a11y page found, and the visual audit flags small light-grey body copy — automated checks only cover part of the picture.

Growth

58

Real problem (discovery on mainstream feeds is pay-to-play), specific audience (indie creators, niche community builders), and a named wedge: curiosity-ranked discovery instead of engagement bait. 25 members is context, not the score.

Improvement areas

  • Mobile Largest Contentful Paint of 10.3s — roughly four times past the 'good' threshold and the biggest technical flaw.
  • Placeholder-looking social proof: identical '5 likes' and '5 followers' counts across 'Viral' and 'Most popular' sections.
  • Missing SPF and DMARC DNS records leave the domain open to email spoofing despite strong HTTP headers.
  • Unlabelled in-app icon rail and low-contrast small body copy hurt first-time navigation and readability.

Design & Usability

Design is the strongest surface here: a dark navy and purple system that actually carries from the marketing page into the signed-in app, a hero that shows the product instead of describing it, and a consistent rounded-card language across sections. The problem is credibility, not craft — 'Viral right now' shows four posts all at exactly 5 likes and 'Most popular' lists creators at 5, 5 and 4 followers, which reads as seed data rather than a living community. Usability is competent: the hero CTA hierarchy is unambiguous, and the /docs page is better than most funded startups ship, with query params, cursor pagination, rate limits and RSS spelled out. The in-app icon rail is the weak spot — five unlabelled glyphs and a 'more' — and small light-grey body copy makes the guidelines screen hard to scan.

Speed & Security

Speed is a split verdict. Desktop Lighthouse lands at 84/100, and CLS 0 with TBT 39ms says the layout is stable and the main thread is idle. Mobile is the problem: 70/100 with a 10.3s Largest Contentful Paint, roughly four times past the 'good' threshold, which points at a heavy hero asset or a blocking render path rather than a slow backend. Security is the best-executed dimension. The header probe returns 11 of 13 checks — HTTPS enforced, HSTS, CSP, frame protection, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and secure cookies all set. The two gaps are SPF and DMARC, which leaves the domain spoofable by email even though the web surface is locked down. The API docs are also unusually candid: the read-only endpoint is unauthenticated by design, and private-community posts are excluded from every response rather than leaked.

Accessibility & Growth

Accessibility scores 80 on the strength of a 98/100 Lighthouse audit with a single failure — heading elements out of sequential order. That is a real but small fix. The caveats are what automated tools cannot see: no WCAG conformance statement anywhere on the site, and a visual audit that flags small, low-contrast grey body copy on near-black, which is exactly the kind of thing axe-core scores as passing while a human squints. Growth is the interesting question. The category — Reddit, Mastodon, Discord — is enormous and structurally hostile to newcomers, and Crowdwide's wedge is specific: curiosity-ranked discovery instead of upvote farming, aimed at indie creators who cannot win a popularity contest. That is a genuine differentiator the site actually demonstrates. The limit is the cold-start problem: a discovery-first network with 25 members has nothing to discover yet, and the placeholder-looking engagement counts suggest the feed is still being seeded by hand.

Conclusion

The honest read: this is a well-built shell around a community that does not exist yet. That is not a failure — every network starts at zero — but the site currently dresses up seed data as momentum, and visitors will notice. The fastest credibility win is not more features; it is either hiding the 'Viral right now' and 'Most popular' blocks until they have real numbers, or labeling them honestly as early activity. Fix the 10.3s mobile LCP, add SPF and DMARC, label the icon rail, and then go get the first hundred members by hand. The thesis is sound and the engineering is real. The crowd is the missing piece.

Suggestions for improvement

  • Fix the 10.3s mobile LCP — compress or lazy-load the hero image and re-run Lighthouse until mobile clears 85.
  • Hide or relabel 'Viral right now' and 'Most popular' until counts are real; identical '5 likes' rows read as fake.
  • Add SPF and DMARC DNS records to close the email-spoofing gap left by the two missing security checks.
  • Add labels or tooltips to the in-app icon rail and raise body-copy contrast above the current light-grey on near-black.
How we score

Alternatives comparison

Named competitors, point by point. Nobody paid to appear here or to be left out.

CrowdwideRedditMastodonDiscord
Discovery modelCuriosity-ranked, explicitly anti-popularity; new voices get a fair shotUpvote-based ranking; popular posts dominate, new posts sink fastChronological feeds; discovery depends on instance and hashtagsNo public discovery; you must already know the server invite
Public APIRead-only /api/v1/posts, cursor pagination, 120 req/min, RSS feedsFull OAuth API with write access, strict rate limits and paid tiersPer-instance Mastodon REST API, open and federatedBot API with OAuth2, gateway events, per-route rate limits
Community scale25 members, 88 posts, 4 communities (self-reported)Hundreds of millions of users across millions of subredditsMillions of users across thousands of federated instancesHundreds of millions of users across millions of servers
Long-form thoughtful postsCore focus — posts, articles and polls with media and hashtagsSupported via text posts, but short memes dominate engagementSupported; character limits vary by instance (often 500+)Possible but buried in real-time chat flow; no public archive
Privacy controlsPrivate communities excluded from API and RSS entirelyPrivate and restricted subreddits; profile visibility settingsPer-post visibility (public, unlisted, followers, direct)Private servers with granular role-based channel permissions

Comparing options? See Crowdwide alternatives, scored side by side

View all Social & Community
Scout Forge

A platform dedicated to providing unbiased reviews of newly launched applications, analyzing everything from their features to their full potential.

info@scoutforge.net

© 2026 Scoutforge. All rights reserved.