Back to articles
Building a "Wevo" - Modeling a Real world promise.

Building a "Wevo" - Modeling a Real world promise.

via Dev.toh1d3mun3

Hi guys :p 👯‍♂ Welcome to Wevo series. As I introduced in my previous post, I built Wevo. https://dev.to/h1d3mun3/introducing-wevo-building-a-trust-history-app-with-swift-vapor-340g In this series, I'll describe how Wevo is built. Let's Dive in. Motivation First, let me explain why I built Wevo. As I posted before, I believe our trust history and related information should belong with us. Trust is built from many properties. History, Details, reactions, date... and so on. So, I believe these information should be in our hands. But in reality, this isn't the case. Our trust history is locked inside platforms. There are many options to create trust in each other. (for example, Slack, linkedin, gmail, X(formerly Twitter), facebook..) If you made a promise on a Slack, and if you want to move promise history to gmail? that's not. you can't move your trust history to other services. This is why I built Wevo. I also had a personal problem: I couldn't remember all the appointments properly. Ma

Continue reading on Dev.to

Opens in a new tab

Read Full Article
2 views

Related Articles