App settings schema - Niblet Docs

Return a schema.Schema from get_schema() to tell Niblet which settings to show when someone configures your app. The runtime recognizes more field types than the hosted clients currently support. This table describes schema vocabulary, not an installability promise.

Field	Use it for
`Text`	A short value entered by the user
`Toggle`	An on-or-off choice
`Dropdown`	One option from a fixed list
`Color`	A hex color
`DateTime`	A date and time
`Location`	A place with timezone information
`LocationBased`	Options based on a selected location
`Typeahead`	A searchable option
`Generated`	Options returned by an app handler
`PhotoSelect`	An image with exact size requirements
`OAuth2`	A provider connection kept outside ordinary settings

Give every field a stable id, clear name, short description, and safe default when the type supports one. Niblet stores the ID with each installation, so do not reuse an existing ID for a different setting.

Load options dynamically

Generated, Typeahead, and LocationBased describe runtime handlers. Hosted schema-handler jobs are not implemented, so these fields currently block installation. Static locations are supported; native Expo image fields remain unsupported.

Keep credentials protected

Reviewed user and publisher credentials are stored separately, omitted from ordinary read responses, and resolved only for authorized renders. General app-provider OAuth is not implemented: declaring OAuth2 does not enable it. Never put credentials into ordinary configuration or MCP messages.

Last modified on August 29, 2026