6
28 Comments

Reached 100+ views and our 1st real user on an algorithm-free social web app

Hey everyone!

​I recently launched Randomverse, a privacy first, chronological social web application built with Flutter and deployed on Vercel.

​Like a lot of people, I got fed up with mainstream social media relying on invasive background tracking, opaque recommendation engines, and engagement loops designed to trigger outrage. I wanted a simple, responsive space where posts show up in real time order and users are not treated like ad data.

​The Week 1 Numbers:

  • ​Around 150 total pageviews

  • ​105 unique views

  • ​1 real sign up: Beyond family and testing accounts, we officially got our first non family stranger to register their handle!

​Going from 0 to 1 registered user on a completely raw indie link felt like a huge milestone for proof of concept.

​What is under the hood:

  • ​Framework: Flutter Web

  • ​Deployment: Vercel

  • ​Core Rules: Zero ad profiling, purely chronological feeds, and built in user moderation tools.

​I am currently focusing on keeping the platform responsive and seeding good content into the feed so lurkers have a reason to hit register.

​Would love for anyone curious about Flutter Web performance or algorithm alternatives to check it out and drop some raw feedback on the UI and UX at https://randomverse-social.vercel.app

posted toAvatar for product Randomverse
Randomverse
  1. 1

    Congratulations on the launch!

    The privacy-first approach and chronological feed are refreshing to see. Wishing you continued growth as you iterate based on user feedback.

    1. 1

      Thank you so much for your kind words, John!

      It’s been an exciting start, and I’m fully focused on iterating based on all this great feedback from the community.

  2. 1

    Getting the first stranger to sign up is a real milestone, much stronger than pageviews alone because someone trusted the product enough to create an account.

    The harder test now is whether they return. For a social app, I’d track activation around actions like viewing several posts, following or replying to someone, creating a first post, and coming back within 7 days.

    Seeding content is necessary, but be careful not to confuse a populated feed with genuine network activity. What specific reason will make the first 20 users return when there are still very few people to interact with?

    1. 1

      Seeding an early feed isn't about faking engagement; it’s about proving proof of concept. An empty social platform is like a ghost town, no one wants to build there until they see what's possible. Populating those initial posts sets the standard, showcases media capabilities, and gives first-time visitors a reason to stay past the first three seconds.

      ​As for what brings those early users back next week, it’s the exact same hook that brought them in initially: uncurated discovery. Traditional platforms rely on algorithms that turn feeds into predictable echo chambers. Randomverse flips that model so every visit is a genuine roll of the dice driven by raw curiosity. Paired with Early Supporter Badges and a direct feedback loop with the builder, early users aren't just passive consumers, they feel like co-builders shaping a fresh community.

      ​Crucially, this design scales without penalizing latecomers. On traditional platforms, algorithms compound reach for mega-creators while completely burying new accounts, or force platforms like YouTube to manually intervene with artificial boosts just to keep small creators visible.

      Here, as the ecosystem grows, overall impression density spreads out naturally, but it spreads equally. Growth never changes the core rule: every active post enters the exact same pool with 100% equal opportunity, ensuring no user whether they joined on day 1 or day 100 ever gets buried.

      1. 1

        That’s the key risk. A populated feed alone won’t create retention.

        For the first 20 users, the loop needs to be: post something → receive a genuine response → return to discover fresh posts while their own content still has an equal chance of being seen.

        Random discovery is the differentiator, but interaction is what gives people a reason to return. So the real metrics are first post, first reply received, and a second session within seven days, not sign-ups.

        1. 1

          I understand your point on retention, but I wouldn't discount sign-ups so quickly as they are the critical pillar for the entire user loop.

          You can’t have first posts or interactions without an account first. On a platform built around real identity, custom badges, and anti-spam integrity, a sign-up represents a major micro-conversion: a visitor trusting the product enough to claim their space. A user who creates an account on day 1 is infinitely closer to creating a post on day 3 than an anonymous visitor who bounces in 3 seconds.

          That's why Randomverse is deliberately designed with an open-door policy for discovery, but a strict boundary for interaction:

          • Zero Friction for Discovery: Anyone can lurk and explore the uncurated feed anonymously without hitting a register wall.

          • Authentication for Participation: The moment a user wants to publish a post, favorite content, accessing profile, or send reports, creating an account is mandatory.

          Requiring an account for write operations isn't just a metric gate; it’s essential for platform health. Without it, an uncurated feed instantly degrades into bot spam and chaos. Sign-ups preserve platform integrity and ensure early milestones actually carry real value for the community.

  3. 1

    Getting that very first organic sign-up from a complete stranger is such a huge validation milestone! An algorithm-free, purely chronological feed is a refreshing alternative to current social media fatigue. Congrats on taking Randomverse from 0 to 1!

    1. 1

      Indeed.

      Thank you so much for your kind words and stopping by!

  4. 1

    The algorithm-free vs privacy-first tension raised in this thread is the right question to sit with. From my own experience building something deliberately non-algorithmic -chronological/curated, not engagement-ranked - the thing I didn't expect going in was that "no algorithm" quietly becomes "someone still has to decide what's worth surfacing," it just moves from a ranking model to a human editorial choice. Chronological solves the trust problem (nobody's gaming your feed) but not the discovery problem (why would a new user know what's good). Curious how you're thinking about that once the feed has more than a handful of posts - does purely chronological hold, or does some curation creep back in as volume grows?

    1. 1

      To me, adding curation as volume grows defeats the entire purpose of Randomverse. The moment a platform starts choosing what's "worth surfacing" it's just replacing an algorithmic gatekeeper with a human one.

      ​Doing that would break the trust of our core users and destroy our main differentiator. Mainstream apps already dominate curated content. Randomverse wins by offering genuine serendipity and absolute user control, not by deciding what users should like. True discovery comes from raw, unfiltered community activity.

  5. 1

    Getting your first real user (not just a view) is honestly a bigger milestone than the 100+ views number itself. What does "algorithm-free" mean in practice here — just chronological feeds, or something more fundamental about how content gets discovered?

    1. 1

      Yes, getting that first user register is the ultimate validation.

      ​For Randomverse, "algorithm-free" means two fundamental things: equal reach and zero surveillance on what you see (not what you post!).

      ​Instead of using a model that ranks posts based on profile tracking, engagement farming, or paid boosts, content flows naturally without being manipulated behind the scenes. It gives every creator a level playing field and gives users a truly unpredictable, raw feed free from echo chambers.

      1. 1

        "Equal reach and zero surveillance on what you see" is a strong, clear stance — a lot of "algorithm-free" claims turn out to just mean chronological, but this sounds more like a philosophy about power distribution between creators and the platform. How do you handle spam/low-quality content without a ranking algorithm to help filter it out?

        1. 1

          We treat quality control as a community and moderation challenge, not an algorithmic ranking problem.

          ​Randomverse relies on community reporting paired with active human moderation. When spam or harmful content breaks platform rules, it gets flagged and removed through transparent guidelines, not silently demoted by a hidden algorithm that penalizes organic posts.

          ​By separating policy enforcement (stopping spam/abuse) from reach manipulation (deciding who gets seen), we keep the feed clean while preserving equal opportunity for real creators.

          1. 1

            That separation is the part that actually clicks for me. Most platforms conflate the two, so a post that breaks no rule can still get buried and the creator never learns why. At least a removal under stated guidelines is something you can argue with.

            What I keep wondering about is what fills the space where ranking used to sit. If reach isn't algorithmically distributed, something else ends up deciding who gets seen — recency, follow graph, or just the luck of posting at the right hour. Have you seen any of those quietly become the new bottleneck? On a chronological feed I'd guess timing starts carrying a lot of weight.

            1. 1

              That’s a sharp observation about timing bottlenecks. On a basic reverse-time feed, posting during low traffic means your work gets buried when traffic surges.

              That’s actually why labeling Randomverse as purely "chronological" in my main post was a misnomer on my part! Strict chronological sorting creates that exact timing trap.

              ​We built Randomverse around an Equal-Opportunity Pool rather than a strict timeline or an engagement algorithm.

              ​Instead of letting a clock or a follower count decide who gets seen, posts enter a neutral candidate pool where every post gets the same baseline chance of being served.

              ​Appreciate you calling out the bottleneck issue. It’s forced me to sharpen how I explain the mechanics!

              1. 1

                An equal-opportunity pool is a cleaner answer than chronological, and I appreciate you being upfront that the original framing was off.

                The follow-up I can't stop thinking about is whether the unit of equality is the post or the person. If every post gets the same baseline chance, then someone posting twenty times a day holds twenty tickets against my one — and volume-posting isn't rule-breaking, so the moderation layer you described earlier wouldn't catch it. That seems like the one pressure point where equal-opportunity-per-post and equal-opportunity-per-creator quietly stop meaning the same thing.

                Is the pool weighted per account at all, or is that a problem you're planning to meet when the volume actually shows up? Totally reasonable answer either way at 100 views.

                1. 1

                  ​That is a fantastic callout, and you hit the exact pressure point, right now the unit of equality is strictly the post, not the creator.

                  ​To be completely transparent at the current early stage, every post gets 1 ticket in the active pool. So yes, under the raw logic today, someone dropping twenty posts naturally holds twenty tickets.

                  ​You're 100% right that high-volume posting isn't spam, but letting a single creator swallow the probability pool purely through sheer volume breaks feed diversity.

                  ​As volume grows, the goal is balancing this to keep the feed fresh and diverse without ever needing engagement algorithms to judge what gets seen, and without leaving old posts to disappear in the void.

                  ​Really appreciate you poking at these exact edge cases, this kind of feedback is super valuable as the architecture scales!

                  1. 1

                    Appreciate you just saying it plainly instead of retrofitting a justification. One ticket per post is the honest description of where it is today, and knowing that is more useful to me than a polished answer would have been.

                    One idea, for whenever the volume actually arrives: the fix doesn't have to involve judging anything. If tickets decay within a window — first post of the day full weight, second slightly less, and so on — a heavy poster still gets more reach than a light one, which is fair, but not linearly more. No engagement signal, no quality call, nothing hidden. Just volume normalization. It keeps the property you care about, which is that nothing about who you are or how popular you are decides whether you're seen.

                    Good luck as this scales — the constraint you've set for yourself is a harder one than most people take on.

                    1. 1

                      I really appreciate this conversation and your thoughtful pushback throughout. It’s honestly been one of the most insightful exchanges I’ve had since launching.

                      Your volume normalization idea is fantastic. Decaying weight per post within a window is a completely deterministic, transparent fix that controls volume without touching content judgment, hidden scoring, or user bias. It fits the core philosophy perfectly for when scale calls for it.

                      Thank you so much for taking the time to dig into the mechanics with me. Hope to see you around the feed as Randomverse grows, and I wish you all the best! 🙏🏼😊

  6. 1

    "Algorithm-free" and "privacy-first" are two different value props. Are people here because they hate the TikTok feed, or because they don't trust Meta with their data? The first wants control, the second wants anonymity. Hard to serve both.

    1. 1

      It’s actually both because in modern social media, they’re deeply connected.

      ​Algorithmic feeds rely on invasive tracking to work. When a platform monitors every single interaction, it hyper-analyzes your behavior to serve tailored ads or "recommend" content based on what you’ve already seen. Even when it tries to show you something "new" it’s still strictly filtered through your past history. You end up trapped in a predictable loop and feeling both surveilled and bored. If you manually look up a topic once, be prepared to see thousands of variations of it for weeks.

      ​I’ve seen countless people complain about both the creepy tracking and these artificial echo chambers (I was one of them). That’s why I built Randomverse to create the breathable, organic space we were all missing.

      ​So far, the response during this organic beta testing phase has been way stronger than expected, all with $0 spent on marketing.

      1. 1

        Love the clarity — "breathable, organic space" is a great north star. But the beta response being "way stronger than expected" with $0 marketing is actually a warning sign. Are you attracting people who want privacy, or people who want a new toy? The first group stays. The second group churns when the next shiny thing launches. Have you tested whether your early users would pay $5/month, or are they just happy it's free?

        1. 1

          To be completely transparent I haven't tested paid tiers yet, and that’s deliberate for where we the project is right now.

          ​We are strictly in a low-friction proof-of-concept phase. The goal today is validating whether the core product mechanics create genuine habit loops and repeat visits. That’s actually why I built the stack so lean (Flutter Web on Vercel with Supabase), keeping overhead near zero lets us test real user behavior without forcing premature monetization pressure on a 1-week-old platform.

          ​Once we establish true retention (users returning week over week because they actually prefer this experience), monetization will come in to cover infrastructure and scaling. The key is ensuring we monetize in a way that never conflicts with our zero-tracking, zero-algorithm core principles.

          ​Right now, retention is the only metric that matters!

  7. 1

    The decision to avoid recommendation algorithms is a strong product constraint.

    What would convince you that users are joining Randomverse because they want an algorithm-free experience, rather than simply because they're curious about another social platform?

    1. 1

      You’re right that avoiding algorithms is a strong constraint, but it addresses a real frustration people face daily on mainstream platforms.

      ​What convinces me users stay for the algorithm-free experience comes down to two sides of the platform:

      • From the consumer side most algorithms eventually lock you into a bubble based on your clicks, serving you the exact same content a thousand times over until your feed feels stale or manipulative. When consumers realize they can actually see new, unfiltered content in real time rather than whatever an AI calculated will keep them outraged or scrolling, the platform stops being just a novelty and becomes a relief.

      • From the creator side on algorithm-heavy sites, smaller creators without thousands of dollars in gear or massive followings get buried instantly. A raw, chronological feed levels the playing field. Creators get excited because their work is guaranteed a fair spot as everyone in front of real people.

      ​Ultimately, if early users stick around, post consistently, and express relief at having a feed they actually control, that’s the ultimate proof that the algorithm-free model is the core value driver.

      1. 1

        Appreciate the context.

        It’ll be interesting to see how users describe the value after spending more time with the platform.

        1. 1

          Absolutely, real user retention will tell the true story.

          I'm focusing on a few non-intrusive ways to capture their thoughts. Time will tell!