Fuchsia

Name	Description
fuchsia.accessibility.gesture
fuchsia.accessibility.semantics
fuchsia.accessibility.virtualkeyboard
fuchsia.audio.effects
fuchsia.auth.oldtokens
fuchsia.bluetooth
fuchsia.bluetooth.a2dp
fuchsia.bluetooth.gatt
fuchsia.bluetooth.gatt2
fuchsia.bluetooth.hfp
fuchsia.bluetooth.le
fuchsia.bluetooth.sys
fuchsia.buildinfo
fuchsia.buildinfo.test
fuchsia.camera
fuchsia.camera2
fuchsia.camera2.hal
fuchsia.camera3
fuchsia.castauth
fuchsia.castconfig
fuchsia.castremotecontrol
fuchsia.castsetup	For internal Google use only. This API is not to be used within the Fuchsia tree.
fuchsia.castsysteminfo
fuchsia.castwindow
fuchsia.cobalt	Cobalt is the Fuchsia service used to log, collect and analyze metrics. The two main pillars of Cobalt are protecting user privacy and providing high-quality, aggregate metrics to serve system and component software developers' needs.
fuchsia.component
fuchsia.component.config
fuchsia.component.decl
fuchsia.component.resolution
fuchsia.component.runner
fuchsia.component.test
fuchsia.component.types
fuchsia.data
fuchsia.developer.tiles
fuchsia.diagnostics
fuchsia.diagnostics.types
fuchsia.driver.test
fuchsia.element
fuchsia.factory
fuchsia.factory.wlan
fuchsia.feedback
fuchsia.fonts
fuchsia.hardware.adc
fuchsia.hardware.audio
fuchsia.hardware.audio.signalprocessing
fuchsia.hardware.goldfish
fuchsia.hardware.light
fuchsia.hardware.network
fuchsia.hardware.power.statecontrol
fuchsia.hardware.radar
fuchsia.hwinfo
fuchsia.images
fuchsia.input
fuchsia.input.report
fuchsia.input.virtualkeyboard
fuchsia.inspect
fuchsia.intl
fuchsia.io
fuchsia.kernel
fuchsia.ldsvc
fuchsia.legacymetrics
fuchsia.lightsensor
fuchsia.location	Types which are useful across multiple location libraries.
fuchsia.location.namedplace	Protocols and types related to named places. Named places include cities, countries, regions, etc. This specifically excludes protocols and types related to latitude and longitude.
fuchsia.location.position	Protocols and types related to positions.
fuchsia.location.sensor	Protocols and types related to sensors.
fuchsia.logger
fuchsia.lowpan
fuchsia.lowpan.bootstrap
fuchsia.lowpan.device
fuchsia.lowpan.thread
fuchsia.math
fuchsia.media
fuchsia.media.audio
fuchsia.media.drm
fuchsia.media.playback
fuchsia.media.sessions2
fuchsia.media.sounds
fuchsia.media.target	A library of protocols for routing media between devices.
fuchsia.mediacodec
fuchsia.mediastreams
fuchsia.mem
fuchsia.memorypressure
fuchsia.metrics	This file contains interfaces that allow clients to log events that are associated with metrics. These events are collected and later analyzed. Metrics are organized under a Project, which are associated with a Customer. Each of these objects has an integer ID and those IDs are used as parameters in the methods in this file. Metrics can also have one or more dimensions associated with them, which are then passed as a vector of event codes when logging the event.
fuchsia.migration
fuchsia.net
fuchsia.net.http
fuchsia.net.interfaces
fuchsia.net.mdns
fuchsia.net.routes
fuchsia.power.clientlevel
fuchsia.power.profile
fuchsia.power.systemmode
fuchsia.process
fuchsia.process.lifecycle
fuchsia.recovery
fuchsia.recovery.ui
fuchsia.scenic.scheduling
fuchsia.session
fuchsia.settings
fuchsia.settings.policy
fuchsia.sys
fuchsia.sys.test
fuchsia.sysinfo
fuchsia.sysmem
fuchsia.thermal
fuchsia.tracing.perfetto
fuchsia.tracing.provider
fuchsia.ui.activity
fuchsia.ui.activity.control
fuchsia.ui.app
fuchsia.ui.brightness
fuchsia.ui.composition
fuchsia.ui.gfx
fuchsia.ui.input
fuchsia.ui.input3
fuchsia.ui.pointer
fuchsia.ui.pointer.augment	These augmentation protocols represent powerful introspection capabilities into the view hierarchy, and must be individually routed to specific target components. Most clients should not have access to these protocols. Some commonalities: - Theory of operation. These augmentation protocols accept a standard protocol endpoint and return an augmented protocol endpoint. In case of error, the original endpoint is returned. - View hierarchy scope. The reach of the augmented protocols are inherently bound to the original protocols they augment. That is, if the original protocol has power over only one view, the augmented protocol gives access to only that view. - Security warning. These protocols enable a form of clickjacking! While the view hierarchy prevents clickjacking of arbitrary views, care must be taken to route these augmentation protocols to the intended view's component. - Security guarantees. These protocols offer Confidentiality, Integrity, and Availability of the augmented data to authorized components. That is, non-authorized components cannot snoop on this data, modify its contents, or prevent its dispatch to authorized components. - Append semantics. Each augmentation provides augmentation-specific data to the protocol's regular event, but otherwise is not intended to modify the original protocol's basic functionality. - Synchronicity. The augmentation-specific data is synchronous with the original protocol's data. - API evolution. Server-side can introduce new methods to these protocols, and new fields to these tables, without breaking existing clients of the original or augmented protocol. For example, [`MouseEventWithGlobalMouse`] can be extended without consequences for [`fuchsia.ui.pointer.MouseEvent`]. - API evolution. When clients require substantially different augmentation, new augmentation protocols representing those capabilities can (and should) be introduced. For example, if one client of [`GlobalMouse`] requires additional fields that are really about view-local hit data, it would be reasonable to mint a new augmentation.
fuchsia.ui.pointerinjector
fuchsia.ui.policy
fuchsia.ui.scenic
fuchsia.ui.types
fuchsia.ui.views
fuchsia.ultrasound
fuchsia.update
fuchsia.update.channel
fuchsia.update.channelcontrol
fuchsia.update.config
fuchsia.url
fuchsia.weave
fuchsia.web
fuchsia.wlan.common
fuchsia.wlan.ieee80211
fuchsia.wlan.policy
fuchsia.wlan.product.deprecatedclient
fuchsia.wlan.product.deprecatedconfiguration
zx