I currently have an API that is gaining traction. I would like to market towards people that are able to use APIs, however there is a technical barrier when It comes to requesting an endpoint, saving data, building a script around that, etc.

Should I build a web application that allows non-technical users to access the data from the API? Or, Is that a waste of time for the effort put in?

  • etchinghillside@reddthat.comEnglish
    4·
    2 months ago

    A querying/dashboard layer for product people to easily interact with - sure. Calling it a no-code solution - don’t do that.

    • Carl@programming.devOPMEnglish
      2·
      2 months ago

      A querying/dashboard layer for product people to easily interact with - sure. Calling it a no-code solution - don’t do that.

      Sorry about that, I simply assumed that was the terminology. Thank you for the feedback, I will most likely create a dashboard for those users.

      • lad@programming.devEnglish
        1·
        2 months ago

        Well, terminology is to call scam promising that even a cat will be able to build a rocket with UI blocks “no-code”.

        Since using “no-code” usually ends up with writing code (usually in JavaScript, afaik), it would be more honest to not call it that, anyway, scammy promises aside