Feedback-Driven Design

Our design team has been on steroids for the past few weeks! Not just crafting those tasty pixels but also a lot of user research and feedback during each step.

We narrowed down the product and customer scope towards the consumer MVP and prepared a clear path of tasks and goals to get there. And this involves a lot of iterations, a lot scrapped prototypes before we arrive to something that we think might work, it's like the theory of evolution — survival of the fittest!

Our product team has been doing a lot of user interviews, researching their models of privacy, communication (and distraction) patterns and habits and attention management challenges. User privacy is the core of our product and what we believe in.


Our platform team has been busy hiring and making great progress on building a solid foundation to pave the way for future product development. We have narrowed down on the schema that we think would be dynamic and flexible to incorporate frequent iterations and new features. Our Swift client is undergoing a huge refactor and Flutter client is catching up real fast! We formulated new goals for this sprint.

Don't forget to checkout our careers page, we're growing and provide a great environment to challenge your intellect and flourish.


The last couple of weeks we've been working and experimenting with a new approach to our organizational rhythm. By collaboratively formulating organization wide objectives, we made sure all of us are aligned on the things we work on, believe in the things we work on, and know why we made choices to focus on the specific objectives, and postpone working on the other objectives. And to quote Michael Porter "Strategy is choosing what not to do", highlights why this is such an important step for us.

Now that we have these objectives the next step is to break them down into Goals, Stories and clear deliverables so they become bite-sized junks of work we can complete in our two-weekly sprints. We're now contemplating to ask each Micro-Enterprise to share their progress at the end of the sprint, so we can celebrate when goals are reached, or help when things didn't work out the way we planned. The process of formulating objectives, breaking them down and especially deciding which objective to follow and which to postpone for now, made us realize that we didn't have enough clarity on how some of the decision making power was distributed. The solution? Deciding how to decide. By creating a "Social Contract" (more on that in future blogs) in which we clearly define which decision making method we use for which type of situation, in this case choosing the objectives, we could move rather swiftly and still incorporate everyone's perspective and concerns to make sure our objectives embodied all of that allowing everyone to feel aligned and motivated to reach them!

CircleUBI Wallet Integration

In this cycle we have completed the UI design for the wallet integration on the front-ends, and improved the CVU files for the views of integrated wallet and cryptocurrencies. In the example, there are two currencies ETH and CirclesUBI that can be added to the wallet. And after signed in, the Cryptocurrency view shows the status details of each currency.

In the next cycle we are planning to build the necessary functions to realize the logic for calling the Omo-core library and handle the queries and data.