Hello all, I would like to discuss some problems I see in how Stitch works compared to other similar tools.
Here the problems I see currently.
Problem 1. Stitch uses SDK’s but for what? SDK’s are pretty 90’s early 2000, Since the GraphQL release, there is no need since you interact with your database only through the API. I know not all people use GraphQL but why not give instant REST API the same way we have GraphQL?
Problem 2. You need the SDK for authentication since Stitch is a ‘Serverless App’ I think the auth logic should be baked in in Stitch without me having to use an SDK, more modern solutions like Strapi give you GraphQL endpoints for Login/Register/LostPassword, so I can simply make a Login Mutation instead of installing the SDK or make a Registration form which triggers a Register Mutation without any packages.
Problem 3 Because all the SDK does regarding auth is storing the token in localStorage is it very hard to keep track of the current state of the User and if he is really authenticated, I know it is easy to check but not so easy to keep track as for example with endpoints that give me more information.
Any chance we will see improvements here?