I have a catalyst application at https://www.ekk.app/ (it is a very basic one and intended to showcase the problem which I am facing).  It is basically a Progressive Web App(PWA) and would like to build an android app for it using Trusted Web Activities( https://developer.chrome.com/docs/android/trusted-web-activity/quick-start/ ). But for a TWA to not show the browser UI(the very difference between a site and app for the users) there is a requirement to serve an asset link file ( https://developer.chrome.com/docs/android/trusted-web-activity/quick-start/#creating-your-asset-link-file ) at .well-konwn/assetlinks.json with respect to the root of the domain or subdomain. Thus whether a site is hosted at https://www.ekk.app/app/ or https://www.ekk.app/server/site/ (both the places at which my PWA is available), the assetlinks.json file needs to be served at https://www.ekk.app/.well-known/assetlinks.json. Unfortunately catalyst does not allow hosting client or functions at the root path and only allows hosting from /app/* path for the client and /server/* path for functions and thus the TWA shows browser UI, thereby making it impossible to host PWAs with android TWA on catalyst.

          So, I request you to allow hosting one single advancedIO function on root path ( https://www.ekk.app/* ) so that catalyst can be used for hosting PWAs with android TWA counterpart(by serving assetlinks.json on ./well-known/assetlinks.json) path. Also, this will help in running some other kind of applications on catalyst(which are currently not possible) such as any application which uses activitypub(building block of mastodon) since activitypub requires that get requests of users at the root path of domain/subdomain returns the user details,i.e., a get request at / path with the query username@subdomain.com returns the user details. In case it is not possible to allow hosting functions, at least allow hosting the client at the root path. Other serverles platforms (like firebase and supabase) allow hosting the client on the root path.

I mailed the same issue at support@zohocatalyst.com on 10th February at 9PM IST but didn't get any response till now and that is why I am posting it in the forum. I understand that implementing a feature might take one or two months, but once an issue is raised it should at least be acknowledged(in this case by sending a response e-mail)