Repository navigation
More Pros and Cons
There are small shortcomings in the current implementation which will be fixed over time. I'm going to skip those here. There are a few core shortcomings which cannot be easily overcome which you should be aware of:
(1) From the browsers point of view, there is no text on the page. The entire page is just one big HTMLCanvas element. This means users cannot search for text within the page nor select and copy text from the page. The latter isn't entirely bad. Even the best of sites fail to correctly disable text selecting resulting in odd states when a user accidentally click-drags a random part of the screen.
Both these no-text shortcomings can be solved within an ArtEngine app via custom search and custom text-copy features. However, we no longer get those features for free. Note that Google-Docs implements custom in-page search which replaces the browser native search, so we aren't alone in solving this problem.
(2) From any web-spider's point of view your app also doesn't contain any text. This means Google search cannot index your site without certain additional steps. The programatic answer is for your web-server to generate a drastically simplified version of your page in HTML which contains the important text for Google's spider. However honest and non-manipulative this is, Google's spider may not like being fed specially generated content. I believe there is an answer here. I will update as we find it. -SBD