Miigen, Library of Life, is a digital legacy platform for preserving and sharing life stories in text, images, and audio, so that milestones and reflections can be passed down across generations. Alongside the storytelling, the platform carries an advertising layer that lets individuals and businesses reach location-specific audiences. Craig came to us at the idea stage, with no existing product to build on.
Memory creators, people browsing stories, and advertisers all wanted different things from the same platform. Each group got a clearly defined space built around what it came to do.
The platform needed advertising revenue without cheapening the experience of reading someone's life story. Ad placements, filters, and content layouts went through several rounds of refinement.
People documenting a lifetime are frequently not the people most comfortable with software. The editor, upload flows, and navigation were designed to be legible on first encounter.
Text, images, and audio in one place usually produces a crowded interface. Category-based organisation and location tagging carry the structure, so the screen stays calm while the content underneath is rich.
We started with low-fidelity wireframes mapping the structure and the flows for each of the three user groups. With an idea-stage product there is nothing to audit, so this is where the product actually gets decided.
A bespoke design system was built for the platform rather than assembled from components, covering typography, colour, and layout across every section.
We ran multiple feedback rounds on the parts carrying the most risk: ad placements, content filters, and feed layouts.
We designed and built the MVP from the idea stage. Memory creators write and publish life stories through a straightforward editor, upload photos and audio, organise memories into categories such as family or travel, and tag them by country, state, and city, with everything stored securely in the cloud. Public users browse a global feed, filter by category and location, and search for specific topics or experiences. Advertisers create image and text campaigns, target them geographically, and manage them from their own dashboard.
Underneath, the platform was built to grow rather than to demonstrate. Laravel carries the backend, MySQL holds the structured data, and Amazon S3 handles media, so photo and audio libraries scale without the platform slowing down.
Miigen went from an idea with no product behind it to a working MVP in two months, covering all three user groups and the advertising layer in one build. It is currently in beta with a group of testers, and memories are being published through it as intended.
The MVP exists to answer one question, which is whether the concept is worth funding, and Craig is now taking it to investors on that basis. What he has to show them is a secure, scalable platform with the architecture already in place for the features that come next.
Yes. Miigen came to us at the idea stage with nothing built. We start with structure and flows rather than features, because on a product that does not exist yet, agreeing what it is comes before building it.
By giving each group its own space rather than one interface with permissions over the top. Miigen serves memory creators, people browsing stories, and advertisers, and each has an interface shaped around what they came to do.
It is built to grow. Miigen's media sits in Amazon S3 and its structured data in MySQL, so a growing library of photos and audio does not slow the platform down.
Yes, and it usually needs the most design attention. Miigen's advertising layer had to generate revenue without interrupting people reading life stories.
A working product rather than a prototype, plus the design system and files behind it.
Frequently, and we plan for it during the web build. Miigen's API authentication was put in place specifically so the mobile phase would not start with a rebuild.
Yes. Miigen came to us at the idea stage with nothing built. We start with structure and flows rather than features, because on a product that does not exist yet, agreeing what it is comes before building it.
It is built to grow. Miigen's media sits in Amazon S3 and its structured data in MySQL, so a growing library of photos and audio does not slow the platform down.
A working product rather than a prototype, plus the design system and files behind it.
By giving each group its own space rather than one interface with permissions over the top. Miigen serves memory creators, people browsing stories, and advertisers, and each has an interface shaped around what they came to do.
Yes, and it usually needs the most design attention. Miigen's advertising layer had to generate revenue without interrupting people reading life stories.
Frequently, and we plan for it during the web build. Miigen's API authentication was put in place specifically so the mobile phase would not start with a rebuild.
Tell us what you are building. We will scope it and give you an honest view of the right approach and what it will cost.