Skip to content

Eventene Evolution Timeline

Eventene has been quietly evolving since 2017. This article is the interpretive layer over the version-by-version archive — the larger story of how the platform's architectural choices and operational pillars came into being.

The short version: Eventene was designed from the start as a coordination layer over persistent people structures, not as an event tool that learned to remember its users. Most of the architecture that supports today's runtime workflows was visible in some form within the platform's first year.

2017 — Foundations

The earliest documented releases (v0.9.1, October 2017) already had Build / Send / Track / Assign as core operational surfaces, a participant Mobile App, and Lists of People as the foundational data primitive. The pre-MVP betas in late 2017 introduced the Undecided attendance state and the foundational tracking-field manifest (Sent / Opened / Bounced / Responded / Checked In / Checked Out). The MVP itself shipped in January 2018 (v1.0) with the Ask / All / Link attendance cascade that still governs Activity-attendance behavior today.

Themes:

  • The Web Response Form was added to the Mobile App in v1.1 (March 2018), confirming Eventene's mobile-first origin — the Mobile App was the original RSVP surface, not the other way around
  • The 3-section Track Summary layout (Attendance / Survey / Email Tracking) stabilized in v1.0.2 and survives unchanged through v4
  • Segmented Lists with Rules (v1.3, May 2018) introduced rule-based segmentation — the architectural ancestor of Subgroups and (much later) of Tags v2

2018 — 2020: Stabilization

Version 2 was framed as a UX rewrite, but its lasting contribution was conceptual: the rename of Lists into Groups and Sections in v2.1 (February 2019). This was when Eventene's data-model terminology started matching what the model actually was — persistent people structures, separate from any single Event.

The Persona model came into focus in v2.5 (July 2019) when "shared personas" became a canonical term, and was operationally completed by v2.9 (December 2019) with Merged Accounts unifying Web App and Mobile App identity. v2.9.5 (January 2020) introduced the Participant View at app.eventene.com/events — the first cross-organization participant home.

Themes:

  • v2.3 (April 2019) introduced Attendance Limits, Waitlists, and Private/Public Custom Fields
  • v2.5 (July 2019) introduced Stripe payments and the 4-step Webform — the architecture that still governs paid registration
  • v2.5.2 (August 2019) introduced the Orders Table
  • v2.8 (October 2019) introduced Custom Branding for Pro/Premier
  • v2.9.5 was the moment Eventene's persistent-participant architecture became visible to participants themselves

2020 — 2023: Operational maturation

Version 3 spanned the COVID era and reflected it. v3.0 (February 2020) opened Eventene to public events with Open Registration — a deliberate market expansion beyond invite-only events. v3.1 (April 2020) added Virtual Event support (External Links, conferencing integrations) in direct response to the pandemic.

The Mobile App was redesigned for v3 in v3.3 (July 2020) with offline support, Persona switching, and virtual-event linking. This was the first major Mobile App redesign and established the runtime app pattern that v4.0 would refresh again.

Late v3 brought operational sophistication:

  • v3.4 (August 2020) brought Check In / Check Out to the Mobile App
  • v3.4.2 (September 2020) added offline Mobile App use with multi-organizer timestamp-based sync
  • v3.5.4 (November 2020) introduced Tags v1 — the schema shipped but operational integration never followed. Tags would remain dormant infrastructure until v4.8.
  • v3.7 (January 2021) added per-Activity Response Timing
  • v3.8 (April 2021) introduced Credits and Packages — cross-Event pre-paid bundles tied to Stripe Products
  • v3.9.7 (July 2021) introduced new User Roles (Associate, Event Staff) and OAuth sign-in (Apple, Facebook, Google)
  • v3.12 (December 2021) introduced Guest Registration
  • v3.13 (January 2022) linked Survey Responses to Group Fields — establishing the data-linking model that v4 would later reverse-direction in pre-fill
  • v3.15 (September 2022) introduced QR Codes for check-in
  • v3.17 (July 2023) added Live Polls via Slido embed — the final v3-era attempt at engagement before v4 brought native Messaging

Themes:

  • The Eventene ID was surfaced (v3.4.5 / v3.5.4) — formalizing per-Person identity
  • QR codes joined the platform vocabulary (v3.15)
  • Multi-Event Credits made participant continuity practical at the payments level
  • Tags shipped as dormant infrastructure
  • The Mobile App became a true runtime operations surface

2023 — 2026: New pillars

Version 4 layered new strategic pillars onto a mature foundation:

  • v4.0 (December 2023) — second major Mobile App redesign; the Digital Badge established as the participant's identity artifact
  • v4.1 (January 2024) — Messaging Center introduced (Event Feed, Activity Rooms, Direct Messages, threaded replies, push notifications). Eventene's engagement layer became native rather than via 3rd-party embeds.
  • v4.2 (April 2024) — Unified sign-in flow and magic link authentication
  • v4.3 (July 2024) — New Mobile App home page; check-in filters; subsequent patches added Microsoft OAuth and email-privacy hardening
  • v4.4 (2025) — Lead Generation introduced: lead capture forms, Collectors, sponsor scanning, online/offline sync. The first system with a third-party role distinct from Organizer or Event Staff.
  • v4.5 (2025) — Points introduced: configurable point-earning actions, custom QR codes for engagement, point totals on the Digital Badge
  • v4.6 (December 2025) — Floating Action Button (FAB) consolidated four scanning workflows into one context-aware menu; activity-card sign-up began dissolving the rigid Step-1 registration model
  • v4.7 (February 2026) — UI polish; Register → Activities, Details → Info
  • v4.8 (April 2026) — Tags v2 delivered: the 5.5-year-old Tags v1 schema finally completed with full integration into Subgroup rules, Track filters, and column sets

Themes:

  • Messaging, Lead Generation, and Points became three named engagement pillars
  • Tags v2 closed a long dormant-infrastructure thread
  • The Mobile App became the operational nerve center, with the FAB consolidating scanning
  • Identity matured: badge + magic link + Microsoft OAuth + Points on badge
  • Registration began to soften from a step-based form into an editable state

What stayed constant

Across all eight years:

  • Groups persist independently from Events. Events reference Groups, not the other way around. This is the architectural decision that made everything else possible.
  • Build / Send / Track / Assign as core organizer surfaces
  • The Event → Activities → People-in-Groups hierarchy
  • Attendance: Ask / All / Link cascade (since v1.0)
  • The four-state attendance model (Attending / Waitlisted / Not Attending / Undecided — Waitlisted added v2.3)
  • The 3-section Track Summary (since v1.0.2)
  • The persona-per-email model (since at least v1.4)
  • The Mobile App as the primary participant runtime surface (since pre-v1)

What fundamentally changed

  • Event Parts → Activities (v1.5)
  • Lists → Groups + Sections (v2.1)
  • Single-event participation → cross-Event persistent identity (v2.9, v2.9.5, then the v3.x identity work)
  • Static 3-step submission → continuously editable participation state (v1.5 → v4.6)
  • Single-organizer events → multi-role coordination (Owner / Admin / Organizer → +Associate / Event Staff → +Collector)
  • Subgroups as the only segmentation primitive → Subgroups + Tags v2 (v4.8)
  • Email-only communication → Email + Messaging Center (v4.1+)

The larger story

Eventene's evolution is most clearly described as moving from event management toward ongoing program coordination. The earliest releases were already pointed in this direction:

  • People living in Lists separate from Events (pre-v1)
  • The persona-per-email model supporting families and multi-attendee accounts (v1.4)
  • Cross-Event Credits (v3.8)
  • Eventene ID as a persistent identifier (v3.4.5 / v3.5.4)
  • Tags as a foundational segmentation primitive (v4.8)

The platform was not retrofitted toward this direction. It was always pointed this way. Each release made architectural choices that supported persistent participation, recurring programs, and operational coordination over time.

That trajectory is still visible in the current Help Center structure — Core Concepts establishes the persistent-people model, the runtime sections (Participant Runtime & Identity, Messaging & Communications, Lead Generation, Points & Engagement) describe how that model expresses operationally, and the planning sections (Plan Your Program, Manage Participants) cover the design-time work.

Where to go next