[showcase] fluent-manager — a lightweight Fluent localisation package built for Flet apps #6333
Replies: 1 comment
-
|
Hi again, Flet community! In my previous post, I introduced fluent-manager — a library I built to simplify Project Fluent integration in Flet apps like CodeUA. Today, I want to share a "Success Story" about taking this a step further: implementing full localisation in a new project without writing a single line of code myself. The Project: H-Line (Hotline App)I’ve been working on H-Line, an open-source tool for the Ukrainian public sector to automate citizen appeals. It’s a more complex project using the Registry pattern and a centralized state container. The AI-Agent ApproachInstead of manual migration, I used a specialized AI Agent Skill. For those using AI-integrated CLI tools (like Gemini CLI), a "Skill" is essentially a package of expert knowledge that teaches an agent exactly how to use a specific library or pattern. I "taught" my agent the fluent-manager skill, and it autonomously:
How to use this SkillThe beauty of this approach is that you can now give your own AI agents the same "expertise." If you are using a compatible agent system, you can install this skill with one command: npx skills add BogdanovychA/fluent-manager --skill fluent-managerOnce installed, your agent knows the Why it mattersBy using an AI Skill instead of just raw prompts:
Links
Localisation is often the most tedious part of app development. Combining Flet, Project Fluent, and AI Skills makes it almost invisible. Would love to hear if anyone else is using AI agents to manage their Flet project's architecture! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone!
I've been working on a Flet app called CodeUA — a social app for the Ukrainian community, available on Android and Web.
While building it, I needed a clean way to handle localisation using Project Fluent, so I extracted the logic into a standalone package: fluent-manager.
How it integrates with Flet
The
FluentManagerinstance is passed through the view hierarchy alongside thepageobject, which fits naturally into Flet's functional view pattern:Wrapping it in a list allows recreating the instance on locale change without breaking references across views.
fluent-manager features
get(key, **kwargs)API.ftlfiles from the filesystemLinks
Would love to hear feedback from the Flet community!
Beta Was this translation helpful? Give feedback.
All reactions