|
|
|
|
|
by robomartin
4645 days ago
|
|
Thanks for sharing. From a technical standpoint I am wondering about the implementation and scalability of such an approach. Are people sensitive to having to wait to download content for their kid's apps? This app only has, as far as I can tell, ten items per subject. Download size is about 70 MB, which means all the content for the available subjects is contained in the one download waiting to be enabled. This is OK for a few subjects and a few items per subject. I can see a more substantial offering grow to hundreds of MB if a similar approach is used. The next approach would be to serve new content off a server when purchased. I really don't have a clue as to whether or not that is seen as a negative when it comes to toddler or young child apps. |
|
To serve from our own server there would be a delay - Apple also has a serve that lets you deliver assets from their server, still a delay, but much faster infrastructure than we could afford.