Native WatchUi.Menu2 Look & Feel

The look/feel of Menu2 can vary by device, and Menu2 has a number of options.

Have you looked at the Menu2Sample in the SDK?

Yes, I did.

But not able to find something like Alerts and Notifications menu. I tested Fenix 6 and FR945 simulators

Try it on a real device.

Also, recall that native stuff isn't written with CIQ.

Yes, I have tested sample Menu2 sample app on real Fenix hardware. It looks same as on simulator.

jim_m_58 said:

native stuff isn't written with CIQ.

Sorry but what do you mean?

Garmin has two different SDK? Private one for native apps and public one for CIQ? 

It sounds quite strange for me. 

The only thing on a device that are written in CIQ are the things you'll see in the app store.  The base firmware and native apps are not written in CIQ but in native code for the device,  They can do things that can't be done with CIQ.

"Native code" doesn't use a VM.  It's compiled for the device and runs "natively" on the device, and likely written in something like c or c++.

Your only way to build apps is to use monkeyC/CIQ.

This blog post is a little technical, but I think it summarizes the reasons for having CIQ apps run in a sandboxed VM pretty well:

https://www.atredis.com/blog/2020/11/4/garmin-forerunner-235-dion-blazakis

Further reading on the Garmin developer website, forum, and a few web searches provides more background. A Garmin-authored presentation provides the justification for a new language and corresponding virtual machine. The Garmin applications, like Java applications, execute bytecode on a virtual machine. Like Android (and the Infocom Z-machine and Java Card systems before it), the CIQ applications are intended to run on a wide variety of devices. Further, the Garmin devices are limited in resources (computation, memory, and battery) and any runtime/OS environment should be able to restrict each client application's usage of these resources. Finally, the Garmin OS and application execution environment need to be able to enforce access control and isolation -- this includes memory isolation when lacking strong virtual memory subsystem within the OS. A badly behaving CIQ application should not be able to bring down the entire watch (i.e., Garmin wanted to be better than Windows 95).

Very interesting reading, thank you for the link!