For audio:

* Have different volumes for different app

* Have one app play its sound on your phone and another app to another device.

* Have two apps play at the same time.

For UI:

* Hide status icons that are just always on and thus meaningless.

* Customize the navigation gestures

* Put apps into windows, split screen, etc.

* DeX for desktop environment when connected to a display -- I can even remote display to my LG TV and the magic remote can be used as a mouse pointer.

For Apps:

* Linux shell and apps (Termux) -- even X windows.

* Firefox, Chome, even Samsung Internet as browsers. Samsung's browser has some unique features for phones and tablets and I end up using it the most.

* VLC for playing downloading media easily on my devices

* Smooth integration with Windows via Phone Link -- notifications, messages, photos, remote access.

* Lots of notification customizations

I could go on. There are so many features that I have never used but that's ok -- we all need and want a different set of features. I use many of these all the time. I used to have an iPhone (and my whole family has i-devices) but I think I'd have trouble going back to such a restrictive environment. But I still fully recommend iPhones and iPads for most people.

> It seems like clickhouse is obviously a big piece of the tech here, which is an obvious choice, but from my experience with high data rate ingest, especially logs, you can run into issues at larger scale. Is that something you expect to give options around in open source?

Scaling any system can be challenging - our experience so far is that Clickhouse is a fraction of the overhead of systems like Elasticsearch has previously demanded luckily. That being said, I think there's always going to be a combination of learnings we'd love to open source for operators that are self-hosting/managing Clickhouse, and tooling we use internally that is purpose-built for our specific setup and workloads.

> I saw what is in OSS vs cloud and I think it is a reasonable way to segment, especially multi-tenancy, but do you see the split always being more management/security features?

Our current release - we've open sourced the vast majority of our feature set, including I think some novel features like event patterns that typically are SaaS-only and that'll definitely be the way we want to continue to operate. Given the nature of observability - we feel comfortable continuing to keep pushing a fully-featured OSS version while having a monetizable SaaS that focuses on the fact that it's completely managed, rather than needing to gate heavily based on features.

> on OSS, I was surprised to see MIT license

We want to make observability accessible and we think AGPL will accomplish the opposite of that. While we need to make money at the end of the day - we believe that a well-positioned enterprise + cloud offering is better suited to pull in those that are willing to pay, rather than forcing it via a license. I also love the MIT license and use it whenever I can :)

> On that note, I am curious what your target persona and GTM plan is looking like?

I think for small teams, imo the options available are largely untantilizing, it ranges from narrow tools like Cloudwatch to enterprise-oriented tools like New Relic or Datadog. We're working hard to make it easier for those kinds of teams to adopt good monitoring and observability from day 1, without the traditional requirement of needing an observability expert or dedicated SRE to get it set up. (Admittedly, we still have a ways to improve today!) On the enterprise side, switching costs are definitely high, but most enterprises are highly decentralized in decision making, where I routinely hear F500s having a handful of observability tools in production at a given time! I'll say it's not as locked-in as it seems :)