squib VS Grape

Use Squib so you can separate design and content. You don't want to get halfway through making your cards when you decide to change things about your layout and then have to make the exact same change to a bunch of cards.

Squib http://squib.rocks/ CIDEr https://www.reddit.com/r/tabletopgamedesign/comments/t7zsoj/new_application_cider_card_ide_for_designing_game/ Cocktail http://cocktail.software/ Paperize http://paperize.io/ PnP_Tool https://boardgamegeek.com/thread/2490834/tool-help-your-game-prototype-tabletop-pnp Dextrous https://www.dextrous.com.au/ nandeck https://www.nandeck.com/ Card Creator https://store.steampowered.com/app/523600/Card_Creator/ Card Creatr Studio https://cardcreatr.sffc.xyz/ Multideck https://apps.apple.com/us/app/multideck/id1193399487?mt=12

Squib! http://squib.rocks

Squib looks like what you want

Then I just printed up a bunch of paper cards with random junk on it. I was using https://squib.rocks/ and art assets from fallout games. I'll see if I can dig up an example but it basically let me turn excel files into decks.

I have begun using Squib. It is written in Ruby, but otherwise seems to do everything you mentioned and then some.

Squib is a Ruby DSL for prototyping card and board games. Write a little bit of Ruby, define your deck’s stats, then compile your game into a series of images ready for print-and-play or even print-on-demand. 833 stars by now

Grape’s support extends to standard conventions, multiple format support, content negotiation, versioning, etc. The complete guide to Grape to develop REST-APIs, test the API and analyze the performance metrics is available on its official GitHub page.

Grape (ruby-grape.org)

I'm very ambivalent about Grape, but this very much reminds me of something I do really like about it: the param validation. https://github.com/ruby-grape/grape#parameters

I am currently working on developing and api using grape and devise jwt for user user authentication.

Your RN app will be making http requests to your server, so it doesn't really matter what backend language/framework you use. If your React work was also utilizing http requests to fetch data, then there shouldn't be much of a difference. If your backend is a simple JSON api, checkout Grape. You can tack it on to any existing Rails app.

I've benchmarked Grape with YJIT and without it (if want to see the code, visit repo)

Grape is a REST-like microframework written in Ruby programming language. Grape is also considered among the best ruby frameworks and can be used to run on top of Rack or can be used to complement the existing web application frameworks such as Sinatra or Rails. The latter can be done through the DSL-based REST-API for communication. The Grape ruby web framework facilitates efficient and meaningful APIs working in the web application domain.

Take a look at Grape - https://github.com/ruby-grape/grape

I love the Grape gem for building APIs - might be worth considering if you are building something new: https://github.com/ruby-grape/grape

Grape is a REST-like API framework for Ruby. It’s designed to run on Rack or complement existing web application frameworks such as Rails and Sinatra by providing a simple DSL to easily develop RESTful APIs. 9,200 stars by now