I am going to compose a series of pieces of electroacoustic music that are:
Stand-alone applications.
Available to a very large number of listeners.
Going to last.
Play indefinitely.
Possibly be user-configurable.
Currently, I am trying to decide the best way to implement and publish these pieces. So far, I have come up with the following possibilities:
[ ] Android applications. Pros: Available to everybody with an Android device. Cons: Not available on other platforms, may become obsolete as Google changes app requirements.
[ ] Web pages hosted on my own private Web site. Pros: Easy to manage. Cons: Won't last long after I'm gone.
[ ] Web pages hosted on GitHub pages, from a new repository designed specifically for hosting these pieces. Pros: Very easy to manage. Cons: GitHub may not appreciate large numbers of users, GitHub may not maintain such a repository after I am gone. In fact there are usage limits, which certainly wouldn't allow "a very large number of listeners." However, it seems that it might be possible to pay a CDN to get in front of my GitHub pages, and thus not run into GitHub's usage limits.
Web pages would use csound-wasm and would also play well on smartphones and tablets.
I am going to compose a series of pieces of electroacoustic music that are:
Currently, I am trying to decide the best way to implement and publish these pieces. So far, I have come up with the following possibilities:
Web pages would use csound-wasm and would also play well on smartphones and tablets.
Still thinking....