About the project
Memora is a private QR-based experience for collecting guest photos and messages while an event is happening. Guests scan a code, enter a name and contribute to the event without creating an account.
Axelyn’s role covered end-to-end product development and production infrastructure, including the guest interface, application services and media workflow.
The challenge
A wedding produces small moments that stay spread across phones, messages and private galleries. Asking everyone to send their photos later creates another task, and contributions can disappear along the way.
The guest journey needed to stay simple while the system enforced event access, ownership, upload rules and valid operations behind the interface. Real event use also brought mobile uploads and operational support into the problem.
Key engineering decisions
Keep the guest contribution flow short
- Approach
- Use a QR entry point, a guest name and a direct path to contributing photos or wishes without account creation.
- Why it matters
- Contributing can fit into the event itself rather than becoming a task for later.
- Boundary
- A short guest flow still needs access and upload checks behind it.
Keep access rules in the system
- Approach
- Enforce event access, ownership, upload rules and valid operations through the application services.
- Why it matters
- The private event experience depends on more than the visible interface.
- Boundary
- Guests do not create accounts; valid event access and operations still need to be enforced.
Connect collection to a lasting archive
- Approach
- Use cloud storage for the media workflow and Google Drive export for the couple’s archive.
- Why it matters
- Contributions can move from a temporary live event into longer-term storage.
- Boundary
- Collecting and exporting files does not by itself tell the story of the event.
How the system works
The guest-facing journey stays narrow. Application services manage the access and media operations behind the private event, with export connecting the collected material to the couple’s archive.
- Private eventA QR-based entry point
- Guest contributionName, photos and messages
- Application checksAccess, ownership and upload rules
- Stored contributionsApplication data and cloud media
- ArchiveGoogle Drive export
Implementation and reliability
The services behind a simple interaction
React and TypeScript power the guest experience. Python services, PostgreSQL, authenticated APIs and cloud storage manage the durable workflow. Event access, ownership and upload rules remain system responsibilities even though guests do not create accounts.
Learn from the event itself
Real event use exposed mobile upload behaviour, instructions, production data and operational support. The product continued to evolve around those observations. Google Drive export connected the live event experience to a longer-term archive.
Results and lessons
Evidence from actual use
The recorded event provides evidence that guests contributed photos through the product in an event setting. The event counts below describe that specific use; they are not presented as a general conversion or performance benchmark.
From a gallery to a story
Collecting files answers what everyone contributed. It does not fully capture what the event felt like. That insight shaped a direction for a curated, scrollable story combining selected photos and messages into chapters.
The lesson carried forward is that storage and the experience of revisiting an event are different product problems. The contribution workflow provides the foundation; the story direction asks how that material should be experienced.