This week, we have been focussing on 5 areas:
1. Iteration 3 of the use-case slides
2. iOS memri browser
3. Pod prototype
4. Incorporation research
5. Hosting architecture plan
Iteration 3 of the use-case slides
We have already had 2 iterations of use-case slide interviews. We have learned a lot about what people like and dislike and what they value. Our ultimate goal is to understand what MVP we should build that provides real value to people and can sustain further development of the technology and support the ecosystem.
In this third iteration we doubled down on explaining better what a memri browser is. We started calling it a "data browser" or a "semantic browser" (though the latter only internally). The two slides below aim to explain the memri buttons and to give an impression of how those buttons are used to look at your data and mix and match it in ways that are useful.
The candidate in our first use-case interview where we showed these slides was very enthusiastic, which gives us good hope for the interviews in the next weeks.
We are working on the first memri browser, which runs on iOS. Think of the memri browser as similar to a web browser such as Chrome or Firefox. Yet, while the internet browsers of today show you websites that hold your data hostage and provide you with a hard to use user-interface, the memri browser gives you full control of your data, in a user interface that you know and can control.
This sprint (and the coming one) has had a focus on refactoring, testing and documentation. At the end of this milestone we will be able to invite others (perhaps you?) to join in and create views within the memri browser. We also did work on the rich text editor component, integrating it into the rest of the browser. The connection between UIKit and the fledgling SwiftUI had some challenges but we succeeded in the end!
We only recently started work on the Pod prototype. The memri pod is the place that stores what we call memri's. These are pieces of knowledge about your world as the screenshot above explains. The memri pod stores all your digital knowledge and interconnects it so that you can easily find it and browser through it in the way that you want. The pod will be open source software that you can run on any computer.
This week our focus has been on integrating the memri browser with the newly REST API of the Pod. The API is an abstract layer on top of the graph database that enables easy syncing (eventually) across multiple devices.
We published a blog post on our research how to incorporate a democratic organization. This is part of our roadmap towards incorporating our organization in such a way that it is inclusive and participatory and fair from a human and economic perspective. Based on this research we will take further steps in setting up a legal form.
To this end we also worked on our requirements document, which we will discuss with various advisors over the next few weeks.
Hosting architecture plan
Lastly, we made good progress figuring out how to make it easy (and affordable) for people to host their pod. We see the intersection between Virtual Machines, Docker containers and microkernels as a possible path towards the flexibility we need to implement future proof security measures.
More on that in a next update! For now, this concludes this week's summary. Take care!