[Future] Make an API for the questions? about 30-seconds-of-interviews HOT 7 CLOSED

@fejes713 We could reach a far wider audience with an api. People will be building their own services around 30-seconds-of-interviews and maybe even some bigger sites would adapt us. All in all, it does not need huge effort and will probably gain us more popularity and usability.

from 30-seconds-of-interviews.

I don't know where we could use that

Once we resolve this we can discuss this topic further.

In my opinion, this has no use case still. The question template might change as well in near future. We're in the early stages and most of this stuff is going to be way different in a month or two once people join the community.

API should be done once we can provide better value to the community. We're at 50 questions, no so far from 100. Let's think about API once we are sure template won't change and our question base is larger than 200 questions. 😉 Shouldn't be that far away

from 30-seconds-of-interviews.

@flxwu You're right. We can implement this 😉 DigitalOcean provided us with free droplet to host this API so we can make us of that.

from 30-seconds-of-interviews.

Due to inactivity, we're closing this as well. Please feel free to reopen this issue if you get new ideas for it.

from 30-seconds-of-interviews.

Can you tell us more about this one? What would be the use cases? Do you have any plans on its structure?

from 30-seconds-of-interviews.

It's not a bad idea to have API that draws from the extracted JSON data, maybe also having an id of sorts per question. That could easily work and might not require a dedicated server (I think there are JSON APIs where you can also update the data). I don't know where we could use that, but it could be nice to have as long as it does not interfere a lot with the rest of the project.

from 30-seconds-of-interviews.

It could even be a local API as long as the questions don't get to large, otherwise we can pull them in and colate them by joining the objects. Then the react just needs to use the next question in series or such. This would also expose the unique IDs for any backend we end up developing, and since react should render fast enough, and this can be pre loaded and cached, this will make repeat visits quick too.

So really I think it's more that a state management question switching script might be more useful

from 30-seconds-of-interviews.