@normandc
the OGRS container doesn't do url containment, so it shouldn't be a problem. The simple webapp creator is just that and just sets the containment url the same as the main url... which rarely works for me.
You can manually change the file on phone via a text editor, with some savy permission changing in the terminal. You will find the installed files in an uncreatively (a good thing) named folder in:
/opt/click.ubuntu.com/your_app_name_here.your_name
@normandc
Edit the .desktop file to configure the url pattern, Webapp Creator is a bit too simple in it's creation of the pattern for all sites to work. For example to get gmail to work I need to add:
--webappUrlPatterns=https?://*.google.com/*
This allows calls to https://accounts.google.com to pass to enable user authentication. While the main url is:
https://mail.google.com/mail/mu/mp/900/#tl/Inbox
For testing you can just remove url confinement to confirm the site works.
edit:
check out:
https://docs.ubports.com/en/latest/appdev/webapp/guide.html
For what it is worth, with the new changes to Unity8 in the dev channel it seems UT is less ram hungry. Plus I'm getting far fewer OOM crashes than on stable. Not sure what has changed, but the OS keeps getting better.
Don't worry, you are far from the only person having troubles with setting up abd. Frankly I have never been on a forum where it comes up, and people don't have problems... seems the nature of the beast unfortunately.
I am waiting on my Pinephone 
I have noticed this too. Ubuntu on my desktop with Firefox and VSC running has a similar footprint to UT freshly booted.
I assume it has to do with having an Android system running underneath Ubuntu on the phone. Both of those things need ram as opposed to just one on the desktop.
AOSP isn't a complete operating system, UT is.
@14v3nd3r
I don't know the reason why, but I do know that UT requires it's own recovery, provided by UBports to work.
How long does the phone need to remain off to justify the battery drain of searching for service?
In my experience standby is pretty efficient... until you are out of service range and searching kills the battery.
Paid apps is a separate issue from things like Snapchat and Instagram.
The 'must have' apps most people want are free anyways as far as monetary cost. What they never think about is what the cost really is: user data gathering and analytics... and those are things the platform fundamentally doesn't enable (nor should it). For this reason we will likely never see these sort of proprietary apps on this platform.
There would also be possible IP problems. Is charging for an app that is a webapp of someone else's site (ie if Pesbuk was paid for) potentially dangerous for the foundation? I don't know... But the Open Store would need to maybe do more in depth checking for paid apps.
Just my first thoughts, and not intented to imply anything about Pesbuk (just an example).