A counterpoint: I found the folder structure logical and not particularly complicated to understand and traverse.

Did you actually look through the folders? There are multiple projects. Theres a wearable project, a phone/tablet project, art (mock ups I guess?), the server code (3, actually. The content, some update server, and a push server), source for 5 library projects (these could just be jars), and documentation.

They do a main, release, and lpreview versions of the app code. I'm not sure why they would do this. Maybe they didn't want to hide it in other git branches? It is example code after all.

A folder for resources and a folder for source is causing you problems?

Yeah, as a developer this immediately intimidates me and I just move on. I thought we were out of the ages of "high ceremony" application structures. Apparently not.