Yes, but first let's make sure we are on the same page:
1. SAFE is basically a key-value database system that runs on-the-cloud;
2. oversimplifying, the basic operations are put(key, value) and get(key);
3. everyone accesses the same database: if you save a key, it's yours and no one else can use it;
4. all data in the network is publicly readable - you can read the content of any key and everyone can read what you saved;
5. only the owner of a key can change its contents, but everyone can read it;
6. you can transfer the ownership or have more than one owner;
7. when you create a new account, the network automatically generates a private/public key pair for you;
8. if you need to save private data, you need to encrypt it - the default way is to use your private key. The content will still be readable by everyone, but it will look like garbage;
9. there are 2 data structures: immutable, mutable;
10. mutable: the above rules (you set a key/value, only the owner(s) can change it);
11. immutable: no owners, you don't set a key, the key is a crypto-hash of the contents, object cannot be changed or removed from the network;
12. immutables are usually to store files;
13. a dns and a network filesystem were built on top of mutable/immutables and are embedded in the network;
14. a browser was built to read this dns / filesystem: it's the "safe browser" (you can access safe sites with "safe://<service>.<domain>");
With all this you can create static websites and put them directly on the network: no servers required.
For dynamic websites (i.e. sites that save/read a database), you don't need to use backend servers. Your JS should directly save/read mutables/immutables. This approach (static websites directly acessing public DBs) already exists and is called "serverless architecture": even Amazon and Microsoft are in this new and exciting business.
If you still need to have some kind of server processing, like a cron, a video converter, or a spam killer processing, you can rely on a server for this (at least its IP/position will be untraceable). But these will be uncommon use-cases, and you should avoid it due costs / vulnerability. Also, you can still develop an alternate coin plus a mining system inside the network, and do the processing without a central server (I think project Decorum does this).
The API is still under heavy changes, so many developers are waiting before start any project. So, there are no many things to see now. As a matter of future, I think Project Decorum is a good one.
I can see a lot of average Joes entering the network to download movies and things like that. I don't recommend to do it (it's not a crime in my country although), but I do think the masses will love the network. And this is also in the privacy category.
I also like targeted ads. There are some anti-capitalists here, but there also some capitalist lovers here, like me. Ad networks like "Google ad-sense" will exist soon or later here. I'll build some if I see a niche. The market will decide if they are useful or not for the network and no one will be able to regulate / ban it by force. I do whatever the market wants.
But for me it's all about infrastructure costs, reliability (no "offline" site, no slow speeds, no interruptions on the service, no DDoS attacks), reduce points of failure, and earning money by providing infrastructure to the network (disk space or network bandwidth - like a mesh) and or with popular content.
DDoS and password leaking, for example.