7
11 Comments

No code API?

At the moment, the no code movement seems to be focused on the frontend side.

There's no code solutions to making web design much easier, and no code solutions to building app prototypes.

But what about the backend?

The idea is to create a no code API platform, where frontend engineers, web designers, agencies, can easily create and access a backend through automatically generated API's (restful, and graphQL).

There's no server to host or manage.

This allows you to gain access to a backend, without ever touching the backend or worrying about how to create a secure API.

Use cases:

  1. Collecting user testimonials. Just set up a backend, then a table, add the fields you want, and use the generated API link to gain crud access to that table.

  2. Collecting emails. Same thing; create a new table, add the relevant fields, and start collecting emails via the generated API.

What do you guys think?

on June 27, 2020
    1. 1

      Exactly like that!

      That's an awesome product. Do you allow users to customize what fields they want? For example if they use google sheets, can they set up custom endpoints to get specific fields?

      1. 1

        Thanks. Yes, I'm working on those features and users can able to do that.

  1. 1

    what about stdlib.com even better you can modify the no code's code! and airtable too

  2. 1

    Hmm... but for people that can't code, they maybe don't even know what an API is.
    I think they still prefer Google Sheet or Airtable for their backend though.
    So what problem you really want to solve?

  3. 1

    I don't think NoCode movement focuses on the frontend. It's focused on building stuff without writing code, so you can legitimately build MVPs (or even full products), including frontend and the backend.

    If you use Coda, Airtable, Glide or million of others, you do have the backend - it's the spreadsheet - and you also have the building blocks for the frontend.

    I think backend is a bit more complicated to "do" without actual coding, in most cases simple models won't work, you will need to build complicated data relationships, and then the whole thing falls apart.

    I'm not trying to discourage you - if this idea "feels" right, keep digging and developing it. You may end up with a great solution to a problem that really exists.

    Good luck!

  4. 1

    I usually turn to Google Spreadsheet or Airtable for that purpose. Can you explain pros of yours over them?

  5. 1

    I think it's a cool idea. But you should make sure you're talking to people who would use it. It's so easy to make these super generic apps (I'm so guilty of this) that don't solve a real problem easily enough.

    Also not sure how you would compare that to something like Firebase. If you're just building something that collects data, there's also stuff like Airtable that has a lot of no-code integrations.

    Also seems a little weird to me calling this nocode, if they need to write JS to use it :)