Building on Dataswyft data accounts isn’t straightforward. Technologists are accustomed to centralized systems, so building systems that are distributed isn’t just a technology skill, it’s a mindset shift.
Why? Because storing data on the user side means users do a lot of the coordination work, much like they do in managing the apps and tools on their phones. That means UX is right in the forefront and good UI is crucial to nudging actions for a well designed application.
Why do it? From our experience, there are usually 3 major reasons for it.
You just don’t want to deal with all the data governance and compliance when you’re trying to take your app global. Great. Giving back data access and control is the easiest way to start for an application. You can keep things the way they are for your app and just synchronize customer data with their data accounts. You can store keys, PII in data accounts and keep your centralized app the same way as before, albeit more securely with double sided encryption. Storing PII on the customer side will also give greater privacy which you can shout about (and be more like Apple).
Want to use customer data of other apps? That is not easily done with centralized systems since no one wants to share customer data. Solution? Give it back to the customer and build an ecosystem with all shareable data within data accounts - even on the enterprise side. Dataswyft’s transaction protocols will ensure that all permissions are given for the usage of any data while the data doesn’t leave the data account system.
Want to transfer data safely, securely while keeping the source of truth immutable? The Dataswyft Data Account Infrastructure helps with that with Dataswyft transaction protocols. You can even append to the source of truth to create a new source of truth if the data is traversing through a chain.