PEA vs an event platform portal
An event platform portal is a logged-in area on a vendor's website where an attendee finds their events. It is browser-based and requires no download, so it clears the most visible barrier. It usually fails on the two criteria that concern the account: personalisation without one, and a lifetime that ends with the event.
The account is the deciding factor
A portal exists because the vendor has a durable relationship with the attendee, and the account is what makes that relationship possible. It is a reasonable design for a platform, and it is precisely what criteria 3 and 4 test against. A portal typically asks the attendee to create credentials, keeps them afterwards, and spans every event the attendee attends through that vendor. That is a general-purpose identity, not an event-scoped one.
The magic-link middle ground
Several platforms have moved to passwordless login, where a link or a one-time code replaces a password. This is a genuine improvement and it materially changes criterion 3, which asks about accounts rather than about passwords. But an emailed code still stands between the attendee and their own ticket, which is a round-trip through a second application at the moment they are standing at a door. Whether that trips the criterion is the most contested judgement on the implementations page, and it is recorded there rather than hidden.
Where the distinction gets thin
A portal that provisions a per-event link, requires no credentials, and caches the essentials offline is a Progressive Event App, whatever its vendor calls it. The categories are not defined by product marketing but by the five tests. Some platforms will pass without ever having heard the term, and that is the intended behaviour of a definition rather than a flaw in it.
Why portals rarely go offline
A logged-in portal has a structural reason not to cache: the content is personal, and stale personal data shown confidently is worse than no data. Solving it means caching per-attendee content and reasoning about staleness, which is real work. It is the same problem every implementation faces, and the reason criterion 2 is the least-met criterion in the market.
References
Last updated 2026-09-04. See the criteria these comparisons refer to.