-
Opening Keynote - Unveiling Odoo 16
Fabien PinckaersHoàn thành
-
Adding features to Odoo PoS : a case study
Iván TodorovichHoàn thành
-
Generate a Ready-to-Deploy Odoo Add-on Directly from UML Diagram
Akhmad Daniel SembiringHoàn thành
-
Patterns and antipatterns in Odoo module development
Alexandre FayolleHoàn thành
-
Towards idiomatic Python with types for the Odoo ORM
Stéphane BidoulHoàn thành
-
How to manage customers' sensitive data and keep them anonymized through the use of a blockchain?
Bléry GeoffroyHoàn thành
-
Glovo's success case: how to deliver groceries in less than 10 mins with Odoo.
Andrés García CastillaHoàn thành
-
How the London Muslim Mosque NGO digitalized its activities to survive the pandemic
Eihab BakirHoàn thành
-
Manage your employees' time more efficiently
Dominik RüttiHoàn thành
-
250+ retail stores rollout in one go
Chintan ShahHoàn thành
Yi has been a software engineer for over 20 years. During that time, he has worked at the world's biggest firms (Apple, Amazon) as well as developing products of his own (https://greenbooks.app) and helped many startups design and launch software products.
He started getting involved in ERP projects in 2019 and quickly fell in love with Odoo. He has been working with Odoo for clients in the US and overseas.
He tries to bring innovation in the consumer software industry to enterprise apps to create the best user experience for business users.
LinkedIn: https://www.linkedin.com/in/ylin
One of my clients, Elite Safety Products*, a distributor of PPE pieces of equipment, had a unique need.
While Odoo worked great for their back office for their sales team, Odoo's user interface for Customers, Sales, and Products was too cumbersome and not so intuitive for these specific users.
For example, when Elite's salespeople talk to customers, they want all information about the customers (invoice aging report, shipment status, analytics) displayed in one place, or when selecting products, they want to see custom price tiers table and real-time status in all warehouses.
With Odoo, some of this information is either impossible to get or requires wading through lots of information the salesperson doesn't need to see. Also, the salesperson is often not great at using software, so the user interface (UI) needs to be extremely simple.
Here is what the product and customer pages look like:
- Product page: https://share.cleanshot.com/IYJceo
- Customer page: https://share.cleanshot.com/intGQh
There were also some technical learnings. To build this app, we decided we need to use a modern SPA (Single Page App) framework like React or Vue for speed of development, and build a completely independent user interface from Odoo. We came up with a way to easily interface with Odoo using a REST API (which is what these frameworks prefer) instead of the JSON-RPC API that Odoo has, and was able to build the custom app in record time.
We think the key learning is that sometimes, you can unlock tremendous user value by having the flexibility to build whatever user interface you want, by using a REST API as an interface and pick an open-source UI framework of your choosing like React. This allows you to build apps to solve a more specific need for your customer. And by using a framework like React or Vue, you can often build UI much faster than with Odoo's native way of extending its user interface. In short, more flexibility, speed, and customer-fit.
This approach is similar to SAP's Fiori project (https://blogs.sap.com/2017/11/19/sap-fiori-app-implementation-custom-apps/), but with Odoo, it is just so much easier. One more way Odoo has a leg up over SAP. We hope Odoo can promote this usage and provide more support for custom apps in the future by presenting Odoo as a REST backend for these apps.
My audience for my talk is developers, functional experts, and end users.
* Case study of Elite Safety Products: https://www.odoo.com/blog/customer-reviews-6/elite-safety-products-odoo-prepared-for-protection-845
?unique=963f712)
