Odoo Community Edition ships with a compact drop-down app switcher that lists installed apps in a small overlay. For teams running many modules across departments, that default launcher becomes a daily bottleneck: it is cramped, hard to scan, offers no visual hierarchy, and gives users no control over grouping, ordering, or branding. The full-page, tiled "home menu" experience that makes navigation feel effortless is one of the presentation refinements typically associated with Enterprise — so on Community you are left with a launcher that technically works but slows every user down dozens of times a day. There is no configuration switch that turns the stock launcher into a proper full-screen grid; it requires real front-end and back-end work against the web client.

ECOSIRE builds a made-to-order Premium Home Menu module that renders the top-level ir.ui.menu records as a full-page, responsive grid of large app tiles. Technically, we ship a standard Community-compatible addon with its own __manifest__.py, a client-side OWL component (or a targeted patch of the web client's app-menu widget, chosen per your Odoo version) that reads the menu tree over the standard ORM/RPC, and QWeb/XML templates plus SCSS assets registered through the module's asset bundles. Tiles are driven by data you control: we extend ir.ui.menu with fields for a custom icon, accent color, and display order (sequence), so administrators reorder and re-theme the launcher from the UI rather than in code. Because the component reads the same menu records the user is already authorized to see, existing ir.model.access.csv rules and record rules continue to govern visibility — no app appears on a tile that the user could not otherwise open.

Beyond the base grid, we tailor the behavior to how your teams actually navigate: optional search-as-you-type filtering across menu labels, keyboard navigation, department-based sections, favorites pinning, and a company logo / color scheme that matches your brand. The layout is responsive down to tablet widths and respects the active Odoo theme and right-to-left locales. Everything is delivered as a self-contained addon so it upgrades cleanly and never patches core files on disk — it hooks the web client through supported extension points, which keeps your instance safe to update.

Delivery is build-to-order. After a short scoping call we confirm your Odoo version (17.0, 18.0 or 19.0), your Community setup, the exact grouping/branding rules, and any edge cases (multi-company, custom themes, portal users). We then build against a copy of your configuration, demonstrate it on a staging instance for UAT, and only deploy to production once you sign off — with a rollback plan in hand. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company layouts, deep theme/RTL customization, and per-department access logic increase the quoted scope.