docuseal VS react-on-rails

Unknown if it's better or worse but https://support.google.com/docs/answer/12315692?hl=en ("Send signature requests & sign documents with eSignature")

and there have also been a bunch of alleged competitors submitted:

https://github.com/docusealco/docuseal#readme https://news.ycombinator.com/item?id=36798593

https://github.com/OpenSignLabs/OpenSign#readme https://news.ycombinator.com/item?id=38052344

https://github.com/documenso/documenso#readme https://news.ycombinator.com/item?id=38404129

but they're all AGPLv3 and the network effect is very real

Docuseal might also do the same and it's open-source

I mostly agree with the author. After working a couple of years with React client render and API a pure server render seems to be a way more productive. For my recent OSS project (https://github.com/docusealco/docuseal) I use server render everywhere except of the 2 most complex/dynamic UI parts (drag&drop form builder and the signing form). I think just figuring out which approach fits best for which part of the software is the most important thing, doing both SSR and CSR in a single project is completely fine when done right.

There are alternatives: https://github.com/docusealco/docuseal

I would like esignatures to be backed by strong electronic authentication, like EIDAS

You should take a look at https://github.com/shakacode/react_on_rails. I created that repo back in 2015 and it's still going strong. Popmenu.com uses it and we've got 5,000 restaurant chains on the Rails monolith and huge traffic and transaction volume. Check out the html source of a popmenu site, like https://110grill.com. You'll see react-on-rails in the source.

It's me, Justin, the guy the started React on Rails and React on Rails Pro many years ago! I'll be following this thread!

The problem is I have no idea how to implement the "remember me" feature in that gem without just making the tokens not refresh for a very long time (I think that would be a security concern). So then I looked more into react_on_rails to just use sessions with Devise as a normal rails app, but I don't know if I'll be able to deploy that on AWS because of the changes I have to do to the webpacker/webpack config to allow for a better folder structure. I've never done that so I don't know if there may be any issues.

I have a production level Ruby on Rails app that is slowly transitioning from pure Rails with JS sprinkles to a Rails backend and React frontend kind of situation using React on Rails.

https://github.com/shakacode/react_on_rails - It was last updated 2 months ago & can do prerendering. I'm not sure why more people aren't suggesting this.

https://github.com/shakacode/react_on_rails use this instead. It's maintained and preferred nowadays

React on Rails is an integration of React + Webpack + Rails + rails/webpacker including server-side rendering of React, enabling a better developer experience and faster client performance. 4,558 stars by now