3 ms·

Nice one. I love the SOLID project, separating apps from storage, and moving the users in charge of their data. This fits really well in that space. Is it poss

Nice one. I love the SOLID project, separating apps from storage, and moving the users in charge of their data. This fits really well in that space. Is it possible to use for users without Javascript enabled? Any plans for a Go API? The HTTP API seems clean enough that it's barely needed, but I guess standardization is good. :) Your pricing page doesn't say if it's monthly or annually.

rgthelen 5y ago
We love the SOLID project as well. We use similar principles and beliefs, would love to adopt their network as it grows as well. Right now the hub is javascript for websites, but we have a React and Node SDK and will be adding more over the coming weeks. Can you chat a bit more about the Go API vs HTTP API thoughts? We are Go fans, just trying to find the right use-case to jump into it. Our pricing is monthly, but always happy to chat about it.
- tommiegannert 5y ago
  > Can you chat a bit more about the Go API vs HTTP API thoughts? I don't think any of my thoughts below are specific to Go. I now see that examples in all languages are simply HTTP requests. I think having a predefined library with, at least, constants (like HTTP header names) and data structures would help having more standardized client code. Perhaps it could even just be a Protobuf definition (there's a hack to use field default values to define constants). Or similar schema language that can easily generate struct definitions/JSON codecs/clients in various languages. Languages that use camel-case (like Java) often benefit from someone central defining the snake-case/camel-case translation to avoid inconsistencies in the code base. Actually, your examples use snake-case for Rownd-defined fields ("revoke_after,") and camel-case for client-defined fields ("additionalProp1.") Caveat emptor: I might be the only person on Earth who is irked by that. ;) A layer on top of that would be a client that sets good defaults. For request building, it could populate headers and sanity-check input. For responses, it could convert HTTP responses to exceptions/errors suitable for the programming environment. For failures, it can help defining which error conditions should be retried and back-off settings. A bonus feature would be to have a fake client (or server) I can use in my unit tests. Something that makes me feel reasonably sure my code will work when talking to your production. That's something I always find more reassuring if the supplier maintains, rather than me.
  - rgthelen 5y ago
    I love the unit test idea. Very cool!
mhamann 5y ago
We're fans of SOLID too! I think there's a ton of interesting work to be done in that space to make it scalable, secure, and really user friendly. We've definitely had some discussions around how Rownd and SOLID might fit together, so stay tuned. From a browser perspective, Javascript needs to be enabled. We'll definitely release an SDK for Go! We're heads-down building SDKs for all sorts of technologies, and could actually use some engineers with a background doing that sort of thing. If that's you, I'd love to chat about it (mhamann@rownd.io)! The pricing is monthly, but if you're interested in more of an annual thing, reach out and we can get you numbers with the annual discount applied. We're working on more self-serve options, which will eventually include the ability to subscribe annually right from the website.

rgthelen 5y ago

We love the SOLID project as well. We use similar principles and beliefs, would love to adopt their network as it grows as well. Right now the hub is javascript for websites, but we have a React and Node SDK and will be adding more over the coming weeks. Can you chat a bit more about the Go API vs HTTP API thoughts? We are Go fans, just trying to find the right use-case to jump into it. Our pricing is monthly, but always happy to chat about it.

tommiegannert 5y ago
> Can you chat a bit more about the Go API vs HTTP API thoughts? I don't think any of my thoughts below are specific to Go. I now see that examples in all languages are simply HTTP requests. I think having a predefined library with, at least, constants (like HTTP header names) and data structures would help having more standardized client code. Perhaps it could even just be a Protobuf definition (there's a hack to use field default values to define constants). Or similar schema language that can easily generate struct definitions/JSON codecs/clients in various languages. Languages that use camel-case (like Java) often benefit from someone central defining the snake-case/camel-case translation to avoid inconsistencies in the code base. Actually, your examples use snake-case for Rownd-defined fields ("revoke_after,") and camel-case for client-defined fields ("additionalProp1.") Caveat emptor: I might be the only person on Earth who is irked by that. ;) A layer on top of that would be a client that sets good defaults. For request building, it could populate headers and sanity-check input. For responses, it could convert HTTP responses to exceptions/errors suitable for the programming environment. For failures, it can help defining which error conditions should be retried and back-off settings. A bonus feature would be to have a fake client (or server) I can use in my unit tests. Something that makes me feel reasonably sure my code will work when talking to your production. That's something I always find more reassuring if the supplier maintains, rather than me.
- rgthelen 5y ago
  I love the unit test idea. Very cool!

mhamann 5y ago

We're fans of SOLID too! I think there's a ton of interesting work to be done in that space to make it scalable, secure, and really user friendly. We've definitely had some discussions around how Rownd and SOLID might fit together, so stay tuned. From a browser perspective, Javascript needs to be enabled. We'll definitely release an SDK for Go! We're heads-down building SDKs for all sorts of technologies, and could actually use some engineers with a background doing that sort of thing. If that's you, I'd love to chat about it (mhamann@rownd.io)! The pricing is monthly, but if you're interested in more of an annual thing, reach out and we can get you numbers with the annual discount applied. We're working on more self-serve options, which will eventually include the ability to subscribe annually right from the website.