popescu-af

Sure, feel free to drop me a line at the email address on the website.

Yes, if you have an iPhone. I didn't find time to complete the android app, but I'll probably do it soon. Should be easy enough since the app is written with react native.

This could very well be used for that IMHO. Other uses could be recruiting platforms, online shops, etc. It's not yet a mature project, but in theory, it can be used for anything that needs user data of any kind.

You make a very good point here. Solid is obviously a considerably more advanced version of what I tried to do here. The main motivation for my project was to ease transactions like registrations, logins and any other forms of identification or information sharing. Like in the case of Solid, my idea was to try and standardize data by organizing it by topics & keys.

The main differences compared to Solid, would be the non-decentralized data storage (smartphone) and the active user involvement in each data sharing transaction, meaning the user has to actively scan a QR code (later other forms can be added like NFC, etc.) for the data sharing to take place (as opposed to Solid, where data can be read indefinitely by an app until access is revoked). An extra thing that Qodebeam provides is (user-supervised) write access, meaning a service can also request to save something in the user data store.

Overall, I'd say it's just a (slightly) different approach to the problem of personal data ownership and sharing. Maybe something that would work well as an intermediate step towards something more advanced like the Solid offering. I hope it makes sense.

You are totally right. Still, the platform could be considered a step in that direction. For example, a further improvement of the terms and conditions could at least force the services to agree not to store any data. If I manage to find at least a service willing to use the platform and some users, it's definitely something to look into.

Edit: I will improve the landing page in the near future, to better show the purpose of it and also to make it less vague.

Nice! I will look into it when I will have some time.

What I have in mind is also past the boilerplate, as you said, changing the design later, while being able to write pure business logic code. Right now, I'm not there because I didn't properly separate the generated files from the ones the dev has to edit. But that would be next.

Hello,

For about 8 months, I worked on a tool that I needed for generating the boilerplate for my microservice-based apps. Today I am releasing the very immature v0.0.1 version, together with a simple example of its usage. There are thousands of things to further include, but I think the current version is already usable to some decent extent.

I really hope it will come in handy to someone as it did to me. Feel free to criticize it ;)

Happy 2021!