This is labeled future because I get ideas and rather than just forget them I write them down. But it doesn't mean I think we should really do it now, soon, or ever. It is just an idea.
As I was thinking today. I realised that this app might get very large if I had many high quality movies. You could save some space for the end result of the movie using the new h.265 for videos with audio. Or you could use GIFV to make it smaller when there is no audio. (or maybe there isn't really a size difference there / h.265 might be better anyway) We could test it.
Anyway, to my real reason why I ask the question. I think it would help with usability and adoption. I want to bring down the adoption barrier as much as possible, but still make an awesome, fun, beautiful app. So, you give them the controls.
That App is just too big for me ...
If someone looks at the app store and sees an app is x.GBs it might be intimidating to download. So to keep it small we could default to not having the larger assets in the db, and then have a useful start up screen so the user could choose the way he wants get those assets. Since it his his choice he will get less mad at us when it fills up their phone, and it gives him the option of deselecting one instead of un-installing when he thinks it is to big.
Start up process
Welcome Screen
Connect to Facebook (Or continue without if you want. But inform them why it would be nice too)
Choose Sync settings (Be informative about which is what and why you would want either)
Download all (Every Update get all of the assets on the phone for offline access)
Get from Cloud over Wifi and Data (REST access to Google Storage) (Still update for riddle and setting changes)
Only Get from the Cloud when connected to wifi (It would just have a place holder image instead of the Hirez videos when you played without Wifi) (Again still syncs game updates, but not asset updates)
First Riddle
Have a discover as you go feeling. As new difficulties show up it would introduce you to them instead of telling you all up front.
This is labeled future because I get ideas and rather than just forget them I write them down. But it doesn't mean I think we should really do it now, soon, or ever. It is just an idea.
As I was thinking today. I realised that this app might get very large if I had many high quality movies. You could save some space for the end result of the movie using the new h.265 for videos with audio. Or you could use GIFV to make it smaller when there is no audio. (or maybe there isn't really a size difference there / h.265 might be better anyway) We could test it.
Anyway, to my real reason why I ask the question. I think it would help with usability and adoption. I want to bring down the adoption barrier as much as possible, but still make an awesome, fun, beautiful app. So, you give them the controls.
That App is just too big for me ...
If someone looks at the app store and sees an app is x.GBs it might be intimidating to download. So to keep it small we could default to not having the larger assets in the db, and then have a useful start up screen so the user could choose the way he wants get those assets. Since it his his choice he will get less mad at us when it fills up their phone, and it gives him the option of deselecting one instead of un-installing when he thinks it is to big.
Start up process
Have a discover as you go feeling. As new difficulties show up it would introduce you to them instead of telling you all up front.