Tag Info

New answers tagged

-1

I don't think this is the proper site for knowing the exact implementation of apple's shuffle: It's going to be patented and highly unlikely to be shared. But, if the question is how are "shuffles" done: Here's a very basic implementation done in pseudocode list<song> songsPlayed = new List<song>(); list<song> songsNotPlayed = ...


1

The simple answer is that in most cases and within reasonable limits yes, it's ok. Some provisos. Copyright law gives you two basic mechanisms, which depend somewhat on the country. In many cases the use small pieces of code copied from a large work is permitted as "fair use" or "fair dealing". The limits are not well defined, but the principle is solid. ...


1

There aren't any download or storage limits for your app (other than available space on the device, of course); if there were, they'd be mentioned in the iOS Data Storage Guidelines. However, you do need to consider how your data files will work with iCloud -- in particular, you should decide whether it's okay for the device to discard your downloaded data ...


0

One good reason to build things with an intermediary service you control is so that you can control your own destiny and control when you need to change the app. For example, if your mobile app was talking directly to google and then they change the API surface you would have to push out an emergency update. This would be doubly bad if the change broke key ...


3

Your suspicion is about right. There really should be nothing that the client couldn't be able to take care on its own unless the server also offered to save information that otherwise could not be saved using Gmail. It could be that, in fact, this is the reason and that Mailbox requires to store additional information. However, I'm more inclined to think ...



Top 50 recent answers are included