Update News without a Website?

Ultimately something like this will be based on some sort of web based updating, whether it is XML or otherwise. There pretty much is no simpler way to disseminate updates without writing some sort of daemon, which is going to be largely out of the question for most people. You could do your updates based on Twitter feeds or something like that, but even that is a web based update at the core. The easiest thing to do is just to turn on "Web Sharing" on your Mac and dump a few XML or HTML files in the document root and learn how to issues your updates that way. That way, once you know it works, you can find web hosting somewhere for pay or for free.

I guess the question is, how do you see yourself updating the data for this app?

 

You don't need to "register a website" in the conventional use of that term. What you need are stored resources that can be retrieved using website protocols, specifically HTTP and/or HTTPS.

Any number of companies can provide such services. Amazon S3 is one example:
http://aws.amazon.com/s3/

If you have ever bought anything from Amazon, then you already have an Amazon account. You simply sign up for Amazon Web Services using your account (no charge for this), and sign up for the S3 service (no charge for this, either). You then use the issued S3 keys to "login" and upload content. By default, uploads are private (readable only by someone with your keys), but you can make it public-readable quite easily.

Your Amazon account will need a stored credit card or other payment mechanism. Amazon bills at the end of each month. Fees vary based on amount of stored data and number of HTTP requests. My last few months have been under 10 cents per month. Obviously, your charges will depend on what you do. If you store nothing and transfer nothing, then your charges are zero for the month.

There are any number of Mac programs that can connect to S3 and upload, download, delete, and manipulate content. I use CyberDuck. It's not hard to find others.

So the basic process goes like this:

1. You upload some stuff to S3.
2. You make it public-readable (or tell the uploader app this before uploading).
3. Everyone can now read what you uploaded, if they know the URL.
4. Amazon charges your credit card at end of month.

S3 has lots of options, such as logging accesses so you can see what is being retrieved, and different tiers of reliability. You can also view the current amount of your charges at any time.

S3 is just one example of a web-based storage service. There are other providers, and other services, such as "compute engine" services like Google's App Engine or Amazon's EC2.

 

That's one of the steps, but it's not the very last one. You'll have to do it when developing your game, so you know it can retrieve the resources from the real storage service URLs. That means you need to setup a storage service while the game is still in development. Not first thing, but some time in the middle to later stages.