Well, it's a standalone, non-hosted, offline application.

If you're designing your own API, you can do all the specs, docs, and if you get it up and running on localhost, you don't even need internet for testing it.

If you want to run a hosted API endpoint, or push your changes to git ofc you'll need the internet, but not because of the application, rather because you're trying to access something else that is not offline.

OK. That's confusing.

Not my product, but I think "offline" means no-cloud. You keep track of your API calls / definitions in your local filesystem/Git server without storing it in someone else's server.

I wonder if this is the time to start pitching "Offcloud" or even "Cloud-free" or even "No-cloud" as opposed to "offline" as a feature ;)

It's nice to have the option to not need an entire online apparatus to make your software function.

Huhh, I think that may not be the worst idea. Feels like there’s room for a better shared language around this shift from everything-as-a-service towards owning your stack. Maybe even bringing back localhost is not the worst approach. Hmmm… just thinking out loud.

SnaS – software, not a service.

That sounds snazzy!

No. You can very much call your project that is running locally without any internet connection.