Wow that’s excellent work! I’m sorry things are crashing for you on the Mac itself, but that could also be due to a number of different reasons and not necessarily the plugins themselves (especially if you’re trying it on a laptop). If you got everything working for iOS though and it isn’t crashing but you don’t see any interface, why not start with loading a website first? That way you eliminate the potential for a file lookup issue or something. In fact the current example project is setup for desktop and while it had mobile support when we added it in 2019 I’m fairly certain that the new example project might not support mobile anymore.
At the end of last year we added support for embedding your entire interface (images and everything) in PAK files using a custom pak:// scheme handler. However this is only supported on desktop using the custom browser that comes with the engine. But on mobile devices the native browser of the phone is used, which won’t support that custom pak:// handler.
That means the sample project probably won’t work anymore on mobile. So I would make sure you test it first using a regular website such as google.com to start. Then you can edit the config in the sample project from DirectoriesToAlwaysStageAsUFS to DirectoriesToAlwaysStageAsNonUFS instead. This will cause your files in the /HTML directory to no longer be embedded in the PAK files and will return to the previous functionality of the example project by copying the entire folder over with the PAK files rather than embedding them.