schickling

12 ms·

1. 91.▲
   by schickling 10y ago

   Thanks a lot for that feedback! I've just created a Github issue for that. Please feel free to add a comment: https://github.com/graphcool/graphql-up/issues/2
2. 92.▲
   by schickling 10y ago

   It's also super easy to embed graphql-up into your own docs & tutorials. Simply add the graphql-up badge as a link and you're tutorial basically comes with a free hosted server.
3. 93.▲
   Graphql-Up: CLI to create a ready-to-use GraphQL API(graph.cool)

   168 points by schickling 10y ago|31 comments
4. 94.▲
   Worldmap chat-app built with GraphQL subscriptions(demo.graph.cool)

   3 points by schickling 10y ago|0 comments
5. 95.▲
   by schickling 10y ago

   Thanks a lot for the shoutout, bh13731. The sunset of Parse and the rise of GraphQL was indeed one of the reasons for us to start working on Graphcool. We have a lot of customers who migrated from Parse to our platform which was a good usab
6. 96.▲
   by schickling 10y ago

   Hi ruslan_talpa, I'm one of the founders of Graphcool. Thanks a lot for your feedback. You're totally right: Not having direct access to YOUR data is one of the main concerns about BaaS which we'll address at its core over th
7. 97.▲
   by schickling 10y ago

   That's a really good point and the foundation for what we're building with Graphcool ( https://www.graph.cool ). It's basically combining a GraphQL BaaS with AWS Lambda (or similar services). We take away the pain o
8. 98.▲
   by schickling 10y ago

   Very good point, mrpoller. DataLoader works great in combination with GraphQL. We're using a similar concept at Graphcool (which is written in Scala using Sangria). This method combined with a smart caching strategy turned out to be ve
9. 99.▲
   by schickling 10y ago

   Hi hobofan (funny name btw), really good questions: 1) BI/Data analysis for non-developers: It's not a feature we're providing yet out of the box but it's on our roadmap for the upcoming months. For now we're focuss
10. 100.▲
    by schickling 10y ago

    That's a really good point, kabes. At Graphcool ( https://www.graph.cool ) we're working on exactly what you're describing. We're putting a lot of work into optimizing for the best possible performance while pr
11. 101.▲
    by schickling 10y ago

    Thanks Robin! I've love what you guys are doing at Apollo! I've just answered a similar question below, so I'll just copy the most important bits here as well: One important thing to note here, is that Relay and Apollo are ta
12. 102.▲
    by schickling 10y ago

    Very good point, morgante! One important thing to note here, is that Relay and Apollo are taking different approaches. Relay provides a great framework which works excellent for a lot of use cases and provides the most convenient and robust
13. 103.▲
    by schickling 10y ago

    Thanks for your feedback scottmf! We're mostly working with frontend developers and trying to simplify their workflows as much as possible. One of the first and most important steps are great learning resources. That's why we&#x27
14. 104.▲
    by schickling 10y ago

    Thanks Jungberg! One of the most common hurdles for frontend developers getting started with Relay (or GraphQL in general) is that you need to build a GraphQL backend first before you can do your first query and start building. That's
15. 105.▲
    Learn Relay – A comprehensive introduction to Relay and GraphQL(learnrelay.org)

    124 points by schickling 10y ago|24 comments
16. 106.▲
    by schickling 11y ago

    This is amazing! Finally payment systems are getting easier to integrate!
17. 107.▲
    Immersive 3D panoramas with your smartphone(demo.optonaut.com)

    16 points by schickling 11y ago|11 comments