Recently while working on supporting our erpnext.com deployment, we observed that a lot of our shop-floor (manufacturing floor) are unable to effectively use the ERPNext mobile application. Many of the forms that they use, like BoM, have fields which are not directly relevant when observing core data (Items in BoM). OR, in case of data entry, they had to make an attempt to navigate through various fields which the web-users needed (so, cannot remove them/hide them).
Overall, we started experimenting with a Flutter based application which can interface ERPNext (v12) and expose some common used functionalities.
Right now we have named the app ‘EBuzz’ - but that was more because of lack of any innovate name than an attempt to link to ERPNext (and no doubts, it cannot work without ERPNext :D)
There is no doubt that there already exists the ERPNext app and many other open-source attempts - we could have used them directly to experiment. Yet, we wanted to work with a from-scratch development because:
- We wanted to create a series of interfaces which have limited fields - whether for viewing or data entry - so that a user in hurry (like people on a manufacturing floor or a on-the-road purchase agent) could easily get what they need. They need not worry about all other fields which are visible for their web-usage.
- Also, in the process of development, create enough small snippets of development (wiki) which a user can use to clone and modify the app without knowing too much of Flutter. So, tweaking for those can afford to experiment.
- Allowing this interface to expand towards the Web (Flutter Web) and Android/iOS alike. Currently this version is only developed and tested for Android - but using Flutter we believe that we would be able to expand quickly.
- An experiment to understand the integration capabilities of ERPNext.
Our focus continues to be developing a raw Flutter application, raw because not much focus on UI/UX, which is easy for a on-the-floor user to use. We will integrate further features/modules of ERPNext in coming days.
We would keep the Github Wiki updated.
Thanks for reading through.
(* We are no experts at Copyrights and Licenses - this project is MIT licensed and hopefully has no infringement over ERPNext/Frappe copyrights. THIS POST OR REPO IS NOT ASSOCIATED WITH ERPNEXT/FRAPPE and neither supported or sponsored by them. Though I would be delighted if there any interest in direction of co-development. )