Newsstand App Backend [closed]

Question

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.

Closed 8 years ago.

I wanted to get some clear "real world" info on what kinda backend is required when running a newsstand app.

The app i intend to make should have the following features.

1. Issues, each issue with a bunch of articles.
2. An Issue can be "Free" or "Paid" depending on how its "Pushed"
3. Auto subscriptions
4. Push notifications
5. Data collection - getting some stats from the users.

I currently have no server, in this case, whats the server requirement? All i want is a print magazine kinda app, essentially a PDF. Is it possible to let Apple host the data with current issues.

Another question besides the server is, how are these Issues packaged? Forexample if its a text file or a pdf?

Any direction would be great

Answer 1

Taking your points in turn:

I currently have no server, in this case, whats the server requirement? All i want is a print magazine kinda app, essentially a PDF. Is it possible to let Apple host the data with current issues.

Apple does not provide hosting for newsstand content. You need your own server for this. It needs to hold the issues, and usually also respond to requests from your app about available and new issues.

Another question besides the server is, how are these Issues packaged? Forexample if its a text file or a pdf?

They are packaged however you like - you tell the newsstand framework which asset(s) need downloading for a particular issue (based on the response youve given about the issues above) Typically you'd bundle it all together in a zip file and unpack / process it on the device when the download is completed.

It's important to note that newsstand is not much more than a framework to enable backgrounded downloads and notifications, and to maintain a library of assets in your app's caches directory. The content and its display is entirely up to you, the developer.