Why did we start working on this?
We want to make the data layer on the client-side less siloed from developers. This is obviously hard because each client's device is remote and is typically part of one-way communication.
Essentially we're building the set of tools that we each wanted as developers building web apps that go into production. One of the main issues we found is that most frontend bugs we've found came from some sort of a data state issue, which got extremely frustrating when the code went into production since you'd have to talk to the customer, get on a call, etc... We wanted a simple way to monitor the user's app, contextualize it in the grander scheme of the data models and application structure, and ideally push out an OTA update that would patch bugs.
What's included
- A simple React library to monitor Redux, and LocalStorage states
- Monitoring user's LocalStorage and Redux states in a clean dashboard, tied together with User data
- Client-side and Server-side API for serverless caching, with support for GoLang and Node.js
I'd love to get feedback on what you think
Mainly I'm interested in these questions:
- Does this solve a pain point that you face as a Frontend developer?
- What features would you want to see built out?
Thanks a ton!
No comments yet.
