DEV Community

Discussion on: How to hide your API endpoints while making an electron app?

 
rhymes profile image
rhymes

I think your best bet is to have a server. Your app calls this server and the server calls Unsplash and other APIs and returns the data.

But what if it's an open source product and there is no way to monetize it. What then?

Open source does not mean you can't possibly monetize it but let'say you really can't because of something. Can you work within a free tier of some service? Things like Google Cloud, zeit, heroku have good free tiers.

You might even be able to do everything within the context of a serverless backend, writing just a thin layer.

It depends on what you're trying to do.

Thread Thread
 
sarthology profile image
Sarthak Sharma

Free tier can be great option.

You might even be able to do everything within the context of a serverless backend, writing just a thin layer.

Elaborate?

Thread Thread
 
rhymes profile image
rhymes

I meant that if the only thing you require is to call an API and get back the result you might not need to build an entire server side application, it might be enough to call a serverless function and let it do it for you.

For example, in this post @didil explains how you might go about writing an API to resize images. In his case he's using a Go library that processes the image but if he wanted (just for our sake) to call Cloudinary's service instead, he would call that, leaving Cloudinary's keys on the server.

Zero servers manually configured.

There's a lot of content here: