new product for fintech company
Hey guys,
I'm building out a new product for our fintech company and have been experimenting with a traditional stack vs convex. Love some of the features and ideologies around convex. I was against using it until I learned internals of how queries and mutations are ran under the hood.
Here's a couple questions I still have around convex for my specific use case.
- The web app is going to be used by an older audience, and they might have legacy browsers. I haven't looked through the convex client side sdk, but do you guys think it's going to be well supported across browsers ( android, ios, web, legacy etc ). I don't think we have to go as far as to support Internet Explorer, but I'm guessing just a level above that.
- The initial version of the app is going to be mostly forms ( kind of like typeform ). User filling out information and going through different screens. In a more traditional stack I might make post requests to the backend after every screen and then do a redirect to the next page. Is there a different mental model while using convex around building screen flow? For eg. In a traditional stack after each "step/screen" I might send a post request to the backend to sync the data to the backend, and redirect the user to the next page from there. But in convex, it's possible to talk directly to convex to sync data from the fe, however I'd have to handle the routing logic from the frontend then.
Any pointers / recommendations would be helpful.
I'm building out a new product for our fintech company and have been experimenting with a traditional stack vs convex. Love some of the features and ideologies around convex. I was against using it until I learned internals of how queries and mutations are ran under the hood.
Here's a couple questions I still have around convex for my specific use case.
- The web app is going to be used by an older audience, and they might have legacy browsers. I haven't looked through the convex client side sdk, but do you guys think it's going to be well supported across browsers ( android, ios, web, legacy etc ). I don't think we have to go as far as to support Internet Explorer, but I'm guessing just a level above that.
- The initial version of the app is going to be mostly forms ( kind of like typeform ). User filling out information and going through different screens. In a more traditional stack I might make post requests to the backend after every screen and then do a redirect to the next page. Is there a different mental model while using convex around building screen flow? For eg. In a traditional stack after each "step/screen" I might send a post request to the backend to sync the data to the backend, and redirect the user to the next page from there. But in convex, it's possible to talk directly to convex to sync data from the fe, however I'd have to handle the routing logic from the frontend then.
Any pointers / recommendations would be helpful.
