Service
OWL FrontendDevelopment
OWL is Odoo's own component framework, and building the frontend in it — rather than bolting on an external SPA — is what keeps a custom screen working after an upgrade. Dashboards, custom field widgets and full client actions that look and behave like the rest of the system.
4 in scope
You probably need this if
Any of these sound familiar.
The standard list and form views cannot show what the team needs
Someone exports to a spreadsheet to get a usable overview
A field needs an input Odoo does not ship
A previous developer added a frontend that breaks every upgrade
In scope
What the work actually covers.
01Client actions — full custom screens inside the Odoo shell
02Custom field widgets that behave like native ones
03Dashboards reading through the ORM, not raw SQL
04SCSS that follows Odoo's own variables rather than overriding them
What you end up with
An interface built on the framework Odoo actually ships, so it inherits the upgrade path instead of standing outside it.
Also available
Next step
Start a projectTell me what the process does today and what it should do instead. I will come back with a scope.