Open teslashibe opened 3 months ago
Had a conversation with Matt and @lacyg4 and the main friction to adoption at the moment seems to be users being non-technical and lacking engineering resources to start utilizing the product. This is the first step to continue investigating how to streamline usage of the product.
Action items: [ ] Investigate possible solutions to issue [ ] Technical conversation with John Durkin [ ] Explore proposal / ideation and move to next steps
Note: In parallel we will continue expanding on data capture channels while we further define this solution
Current plan: @teslashibe
After a product strategy analysis and analyzing the major pain point being time to usage and understand across customer integrations is at large. Instead of the SaaS API we will invest in a dev playground and datasets that are not nested within a SaaS API solution for now. We have decided to expose the playground and datasets that support major use cases instead. Allowing users to quickly understand the value of the data and use cases. This will allow us to quickly.
cc: @Luka-Loncar @lacyg4
For reference areas of development of the research that was done. This is part of another ticket where we will define the playground and datasets.
Stickies in purple focus on the playground and datasets: https://github.com/masa-finance/roadmap/issues/37
Currently some non-technical users of the protocol may not be able to run a node in their own infrastructure, do we host an API and develop a SaaS model on our front end (API)?