- The Eng team ships continuously, but new features sit gated behind flags and see little real use
- A compelling product is built through iterative releases and tight stakeholder- and user-feedback loops
- Concept: a sequence of releases building to the RemiliaNET 2.0 Public Beta, targeted for a December 2026 – late January 2027 window — the platform launching as one coherent, marketed product
- Along the way, every release ships to Hot Pot and other trusted testers — feedback arrives continuously, not at the end
- 3-panel + widget 2.0 UX — three panels (guild / stream / media browser) + reworked Profile, Tab rotation; widget layer — draggable show/hide overlays above the panels (e.g. BeetleBoy, remicast) so you needn't hide chat or timeline to use them
- Chat — new global, group chats, DMs, HRT, media, reactions, moderation
- Content — articles/blog, comments, lists, save/like/love, chronological timeline
- Media browser — the user's media tab: an are.na-like, atomized personal collection of saved media, articles and lists; built on the Booru's database structure
- Guilds — joinable rooms with identity: full role hierarchy + granular permissions, channels, invites, badges
- Notifications — unified notification center
- Mobile — PWA-first (Hot Pot testers are primarily phone users, mostly female). Manifest + standalone display are already wired; mostly mobile-responsive UX, install prompt, and push polish remain. Stretch: a slopped Swift or Flutter shell for App Store presence
Working proposal subject to change
Adjacent, launching on independent timelines: Booru (the public milady-meme database/site) and MiladyMaxxer
- Chat — HRT global chat, replies/images/videos/DM-creation merged and live in staging. Global Chat Moderation MVP in progress (ENG-1987). Read-receipts/unread-counts decomposed into backlog tickets.
- Content — posts schema + blog editor + a basic published-blogs timeline shipped; comments/lists/Like-Love-Save not yet.
- Booru — votes, favorites, comments, tag diffs, Gemini autotagger all in prod. Upload moderation queue in review. Ready for Eng Dogfood.
- Guilds — DB foundation merged (schema, invitations, applications + voting); web/UI freshly ticketed (ENG-2005/2011-2017), all backlog.
- MiladyMaxxer — recommender deployed to prod; new-model training-data curation already started (ENG-2018); Chrome Web Store + legal/consent work ticketed.
- Mobile / PWA — manifest + standalone display shipped and linked from
index.html. Responsive coverage and install/push UX outstanding.
How to read this: each release ships to a widening audience — eng → Hot Pot + trusted testers → public. A feature under a release ships in that release; this is not a "things we're working on" list. The Public Beta is when the full 2.0 platform goes public as one coherent, marketed product — individual low-risk pieces may reach the public earlier as they're ready. Release 1 is firmly scoped; later releases are intentionally lighter and detailed closer to the time. R3 and R4 in particular will almost certainly resequence as scope on the new UI and Guild dependencies settles.
Release 1 — Chat + Posts The core social loop, shipped as one drop so the two amplify each other — you come to chat, you post, posts surface back into chat.
- Chat: global chat (HRT, media, reactions) + moderation MVP
- Posts: articles/blog, comments, lists, save/like/love, chronological timeline
Release 2 — Messaging
- DMs, group chats, unified notification center
Release 3 — reminet 2.0 UI* The 3-panel desktop shell, widget layer, and new visual language — sequenced ahead of Guilds because Guilds likely depend on the new shell to land properly.
- 3-panel shell + widget layer + media browser
- New visual language; reskinned surfaces
- QA pass on the new UI
Release 4 — Guilds + Mobile, then Public Beta*
- Guilds: create/join/leave, guild page, #main + #announcements channels, badges, full role hierarchy + granular permissions (owner / officer / member + custom), management dashboard, invites
- Mobile: PWA polish (responsive coverage across the 2.0 shell, install prompt, push), plus optional Swift / Flutter wrapper spike for App Store
- Target window: December 2026 – late January 2027. The 2.0 platform launches to the public as one coherent product
* R3 / R4 ordering depends on how the new UI and Guild dependencies resolve. Mobile could lift earlier into R3 if PWA polish lands sooner; Guilds could stay paired with the UI work or split off.
Booru and MiladyMaxxer run as independent parallel tracks — Booru (the public milady-meme database/site, classic frontend) toward its own indexable launch, seeded after dogfood + QA; MiladyMaxxer toward its public extension release (~2-4 weeks out).
- Media browser depth — the full are.na / pinterest / camera-roll vision: notes, links, rich content classification and navigation
- Additional widgets — remicast (picture-in-picture streaming) and beyond
- Widget-ify BeetleBoy + add new game modules — bring the existing game into the widget layer; new cartridges (e.g. gambling, fishing) in the carousel
- Guild reach — applications + admission voting, home/associate affiliations (3+5), guild subscription, content tagging → propagation, #officers/#media channels
- Social graph ("The Graph") — following (hidden follower counts), friends-of-friends access, match scoring, blocking; the relational-graph layer underpinning discovery and recommendation
- Algorithmic / tribal-weighted timeline (full tribal truth) + digital tribe formation/clustering, with the MM recommender feeding it
- Economy — points, cosmetics, gacha, marketplace, premium
- Exocore — passive capture, notes, voice capture, SRS
- Seasonal leaderboards, guild leveling / widgets / themepacks
- Full invite-only onboarding — invite accumulation, per-guild newcomer gradient, targeted seed-guild funnels
- Voice chat, TCG, sub-guild formation, virtualization
- Native mobile (post-PWA) — full App Store / Play Store presence beyond the slopped wrapper, depending on adoption
- Pictochat — prototype being mapped by Onno