3 ms·
This is very well put together! The API feels very natural and has an obvious flow to it, easy to work with. The vast majority of Firebase projects should have
by krono 5y ago
This is very well put together! The API feels very natural and has an obvious flow to it, easy to work with.
The vast majority of Firebase projects should have their needs more than covered by these endpoints/services. I doubt Google would mind if you were to take some of those lower-end customers off their hands ;)
In order to make this comment look less like a paid endorsement: I couldn't find the upstream sources or info on your pre-processing of the data endpoints (news, stocks, etc.). Sadly without this information they are quite useless.
I can see this going places.
- asim 5y agoThanks for the comments. Yea so we used to say "Powered By X" to indicate what the APIs were backed by but it was a little hacky. We'll try to reintroduce something back into specify the "source". You can otherwise see all the source code for the services in a monorepo on GitHub https://github.com/micro/services https://github.com/micro/services. Would be interested to get feedback on a better way to make it available.
- krono 5y agoWoah, open source too, that is awesome! I'm currently learning Go, will try to get a PR in later this week. Considering this public availability of your data source implementation details, a basic provider name listing somewhere in the docs would be good enough for me!
- asim 5y agoI really want to try make it all programmatic but yea in the docs is probably the easiest to start. Thanks for the feedback. You can see the rest of the source for the site and client libs in https://github.com/m3o https://github.com/m3o. I'm separating Dev UX from the actual underlying platform and services in the hopes that others might also build things around them.