Local governments are actually very supportive of former criminals who were penalized for cannabis-related infringements. If you want to drop a resume, we can certainly see if there’s a good fit! Feel free to email [email protected].
Our solution is both software and infrastructure. On the infrastructure side, we our own distribution license, fleet of trucks, warehouses, and more. And that's all wrapped under our web portal to help make shipping and compliance easy.
We're METRC approved and working on the integration now. API is on its way too.
We have openings in Oakland and LA for engineering, design, data science, HR, and supply chain. Reach out directly if you or anyone you know might be a good fit!
We've noticed the similarity in name and currently we work specifically in the cannabis industry, so it's differentiated by our scopes of work as they do general packing and shipping.
Thanks for sticking with Scaphold. We'll be bumping up the power of permissioning soon! We've been focused on implementing more features with our schema and custom logic in the meantime :)
It's always good to see more companies push for GraphQL.
There are a few others like this, one of which I co-founded, called Scaphold.io (https://scaphold.io), and we're huge proponents of GraphQL and Serverless as well. It truly is the future of app development.
If you're interested in learning more about using Serverless with GraphQL, feel free to join the Serverless GraphQL Meetup that we're hosting (https://www.meetup.com/serverless-graphql).
Great question! There are great libraries like Create-GraphQL (https://github.com/lucasbento/create-graphql) that can help you scaffold an app on the server side pretty quickly, and it's fairly un-opinionated. That one in particular works with Mongo, but I believe they're rolling out support for other data sources as well soon.
In addition, if you're looking for a hi-fidelity way of building apps without having to worry about the server-side, Scaphold.io (https://scaphold.io) is a GraphQL backend as a service that can help. I work full-time here, and we help you get from zero to GraphQL in a matter of minutes.
And with this you have two options:
1) If you want to use the service, by all means :)
2) We're built to the open standard / Relay spec, meaning that if you want to create an app to learn about how the API is structured, that can help as well. Here's more of a primer on how our API is built and works anywhere (https://docs.scaphold.io/coredata/schema/).
Very excited as well for the release of Relay Modern! I think overall a huge boon for the Relay developer experience.
I'm with you here on the static queries. We've used Relay a couple of times as well for various smaller applications here and there, but honestly felt the "magic" was too strong. I'm looking forward to building my future apps and try out Relay Modern.
In addition, I want to be able to encourage more applications that build on our GraphQL platform called Scaphold.io (https://scaphold.io) to try out Relay Modern as well since our API is built to the Relay spec. With that in mind, I'm hoping that the spec will be less restrictive in the future, so there's a smaller learning curve for folks trying it out.
As for the concern with focusing on the internal needs of Facebook, I think the experience that they have working with one of the largest distributed systems in the world helps (rather than limits) their vision on what Relay can be. I trust that this is the case, though it would be really great to see some of the tooling for native support (i.e. iOS, Android, etc). I'm sure they've got that somewhere waiting to be released as I can imagine they have plenty of mobile teams at Facebook who aren't using React Native yet.