For visitors
A personal concierge helps a signed-in person find suitable events. Event cards refer to records in the application; prices and event details come from the same source as the rest of the app.
TYDE
ADAM proposes. A person decides.
TYDE is a nightlife, ticketing and social platform. Its product design connects native iOS and Android apps to a shared API, with ADAM as an assisting AI layer.
VF / 01REFERENCE ARCHITECTURE
- Visitor · Organiser: NATIVE IOS / ANDROID / API
- Permissions and existing records: PERSONAL / ORGANISATION SCOPE
- Concierge · Draft proposals: READ / RANK / DRAFT
- Human approval and audit: APPROVE / EXECUTE / RECORD
INSIDE THE BOUNDARY
Every layer has a purpose.
Personal conversations and organisation proposals retain distinct data scopes. The design connects suggestions to existing records and sensitive actions to human approval.
For organisers
An organisation-scoped queue of insights and drafts: for example, ticket-sales signals, a lapsing audience or a news post. Staff can approve or dismiss a proposal.
Approval turns a proposal into an action
The design requires human approval for a specific message, publication, charge or price change. Execution is attributed to the person who approved it. The server calculates financial amounts.
Product in development
This page describes the product and integration design. AI integrations are being validated further before rollout. Availability and final hosting will be defined at launch.
WHAT YOU GET
Native apps
Swift/SwiftUI for iOS and Kotlin/Compose for Android, with a shared API contract.
Personal context
Visitors get their own conversation within their account’s scope.
Organisation context
Insights and approvals follow permissions within the organisation.
A shared AI pipeline
The integration pattern connects apps to the local or European AI services configured for deployment.