Skip to main content

Show HN: Prototype – build GraphQL backends without code https://ift.tt/33f2boR

Show HN: Prototype – build GraphQL backends without code Hi HN, We're Rishabh, Aashish, and Noah, the creators of ProtoType: a platform for building GraphQL backends. You can check it out here: https://ift.tt/2oOmaf4 We were fed up with creating the same sort of APIs over and over again when building web applications so we built this tool for ourselves. As we're all in university, we showed it around to our friends and they enjoyed using it to kickstart their projects. After that, we thought we'd host it on a website and allow anybody to use it! ProtoType is different from similar GraphQL backend builders such as 8base in that it focuses on data modeling. All you need to do is model your data then hit deploy (no dealing with relational tables). Once you hit deploy, ProtoType will automatically generate and deploy a GraphQL server that supports your data models. On the roadmap is migrations, tutorials, roles/permissions, live server logs, and data metrics (how much your models are created, read, updated, and deleted). Looking forward to all of your feedback! The ProtoType team November 5, 2019 at 05:52AM

Comments

Popular posts from this blog

Launch HN: Simmer (YC W19) – Reviews for Delivery Dishes https://ift.tt/2Y4sD67

Launch HN: Simmer (YC W19) – Reviews for Delivery Dishes Hi HackerNews community! We’re Vaibhav and Richard, founders of Simmer ( https://usesimmer.com ). Simmer aggregates dishes from DoorDash, Caviar, GrubHub, and basically every other delivery platform out there, and tells users the best dishes across the board. We do this by providing dish-level reviews. Users find highly reviewed dishes on Simmer, choose the delivery platform of their liking, and we deep link them into their chosen delivery app. We essentially lead gen to delivery. We started working on Simmer because we loved trying new restaurants, but never knew what to order. Especially, when there’s a 5 page menu. We always asked ourselves, “Why aren’t there ratings for individual dishes?” We launched our app with this restaurant-centric use case (reviews for every dish at every restaurant), but when we rolled out delivery integrations, we realized that users resonated most with the delivery angle. They found it particularly ...