Skip to main content

SaaS-FrameWork

Reusable SaaS UI components for Flet: a versioned design system with 75 catalogued components — buttons, inputs, navigation, data tables and tree views, charts, overlays and dialogs, feedback, media and responsive layout — plus accessible color themes and a navigable component catalog.

Install

pip install SaaS-FrameWork

For web deployments, install the web extra:

pip install "SaaS-FrameWork[web]"

Quickstart

import flet as ft
from components import DEx_BtnPrimary, DEx_MetricCard, DEx_Notify, DEx_TextField


def main(page: ft.Page) -> None:
    page.title = "Hello SaaS-FrameWork"
    name = DEx_TextField(label="Your name", hint="Type and press the button")
    page.add(
        DEx_MetricCard(label="Active users", value="1,024", delta="+12%"),
        name,
        DEx_BtnPrimary("Greet", on_click=lambda e: DEx_Notify(page, f"Hello, {name.value}!")),
    )


ft.app(main)

Save as hello.py and run:

python hello.py

Every public component is importable straight from components (from components import DEx_DataTable, DEx_AppShell, ...).

Compatibility

Requirement Version
Python >= 3.13
Flet == 0.84.0 (pinned)

The Flet dependency is intentionally pinned: Flet's API still moves between releases, so upgrades only land here after the project's upgrade policy revalidates all 70 use cases against the candidate version. Installing this package therefore also pins your app's Flet version.

Component catalog

Browse every component, its use case, parameters and source in the live catalog:

The catalog has global search, maturity filters and a responsive layout, and is audited for accessibility (WCAG AA contrast, keyboard navigation).

Versioning and maturity

The project is pre-1.0: APIs may still change between minor releases. Each component declares its own COMPONENT_VERSION and the catalog groups them into maturity bands — Experimental (0.0.x), Evolving (0.1.x+) and Stable (1.x+). Every component change that touches behaviour is required (and enforced by the test suite, locally and in CI) to bump the component version; docstring, comment and formatting-only changes are exempt. The version header of each component's .md is checked against COMPONENT_VERSION as well. Release history lives in CHANGELOG.md.

Feedback

Bug reports, questions and suggestions: https://github.com/DEx-SaaS/FrameWork/issues

Development

Contributor documentation — folder structure, naming conventions, versioning rules, test suite and the component contract — lives in CONTRIBUTING.md.

License

MIT.

Metadata

Release files for SaaS-FrameWork 0.1.17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for SaaS-FrameWork 0.1.17
File Size Uploaded Provenance Actions
saas_framework-0.1.17.tar.gz 97.8 kB Without provenance Details for saas_framework-0.1.17.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for SaaS-FrameWork 0.1.17
File Interpreter ABI Platform Actions
saas_framework-0.1.17-py3-none-any.whl Python 3 none any Details for saas_framework-0.1.17-py3-none-any.whl

Total release size: 232.5 kB

Release files / saas_framework-0.1.17.tar.gz

Download URL saas_framework-0.1.17.tar.gz
Size 97.8 kB
Tags Source
SHA-256 checksum
How to use checksums
4431fdfce151bba737855dd9b75cec93bdd2afa5289fb618e8931c03b30a004f
BLAKE2b-256 checksum
How to use checksums
9a0a763ea98a685864675c2ea33d5c730ba7e4e17ff219048a4558784ecfdd39
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Release files / saas_framework-0.1.17-py3-none-any.whl

Download URL saas_framework-0.1.17-py3-none-any.whl
Size 134.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7cf0eb758621ef57f120b87780890eb94cb39869186c044ced12439e9b7745d3
BLAKE2b-256 checksum
How to use checksums
9f2528fd08cdedb064cd35054b1425aba0d74f50744c1c912eacbd6b0da25b4c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Security for SaaS-FrameWork 0.1.17

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page