It's not your/my/our job to wonder what resources might be needed to keep it running. If you build a service like this, you should have a user-friendly exit plan.
At the very least they could be open and honest about what is going on instead of pulling a "thanks for being part of this incredible journey, we've had our fun so now we will let you stand in the rain".
"thanks for being part of this incredible journey, we've had our fun so now we will let you stand in the rain"
There's nothing fun about shutting down a company and putting people out of work. Also, standing in the rain is being dramatic.
Yes, it's expected that a service provide you wait an export feature when they shut down but you also need to consider the ramifications of a company shutting down: people jump ship. And rightfully so. They have families that they need to take care of and looking for another job is #1.
If you're this concerned about being able to export your data, don't start using a company unless they already have data export feature available and publish a detailed user-friendly exit plan in advance.
Presumably, this company sent out emails to everyone notifying them of the closure and export feature. Yes, 2 weeks is a little short but I understand the complicated logistics of extending the export timeline.
At the very least they could be open and honest about what is going on instead of pulling a "thanks for being part of this incredible journey, we've had our fun so now we will let you stand in the rain".