Android mobile application in Python to control the maintenance of computers in sectors of a company with real-time database -Firebase.
The idea of this project is that the employees of a company can make maintenance requests when necessary. In addition, they can follow the progress of calls within a screen called "Queue".
Each user registers with their name, email and company sector. From there, it can execute a call and be recognized in the request queue.
The maintenance team has its own interface for the application, where it can create new categories of problems, test submissions and access the list of requests. In addition to monitoring case statistics in real time to assist in decision making.
See requirements.txt
This app was built using Google Colab.
In a new notebook, load all the files and folders that will be used in the project as in the scheme below :
After joining all the files, run the scripts below one by one
!pip install buildozer
!pip install cython==0.29.19
!sudo apt-get install -y \
python3-pip \
build-essential \
git \
python3 \
python3-dev \
ffmpeg \
libsdl2-dev \
libsdl2-image-dev \
libsdl2-mixer-dev \
libsdl2-ttf-dev \
libportmidi-dev \
libswscale-dev \
libavformat-dev \
libavcodec-dev \
zlib1g-dev
!sudo apt-get install -y \
libgstreamer1.0 \
gstreamer1.0-plugins-base \
gstreamer1.0-plugins-good
!sudo apt-get install build-essential libsqlite3-dev sqlite3 bzip2 libbz2-dev zlib1g-dev libssl-dev openssl libgdbm-dev libgdbm-compat-dev liblzma-dev libreadline-dev libncursesw5-dev libffi-dev uuid-dev libffi6
!sudo apt-get install libffi-dev
!buildozer init
Note: after running !buildozer init, make sure the buildozer.spec file appears. If not, click the update files button in the files panel.
Configuring buildozer.spec
-
Double click on the buildozer.spec file. On the opposite side of the screen, the settings of this file for editing will appear.
-
Delete everything and paste the entire contents of the buildoze.spec file that is attached to this project.
-
You can configure buildozer.spec in different ways according to your project. For more information visit: https://buildozer.readthedocs.io/en/latest/
-
After all this, run
!buildozer -v android debug
When the whole process is finished, a folder called bin will be created and inside it will contain your .apk file ready to be sent to your Android device. Download the file and transfer it to your mobile device.
- Register at https://firebase.google.com/
- Create a new project
- Follow the steps for configuration
After that, inside the console from Firebase:
- Set a new
Webapplication - Register your app
- Click in
Realtime Databaseon the left side of the console andCreate Database - Follow the steps for configuration.
At this point your realtime database has been created.
Go to Project Overview at the left side of the console and click on the gear icon. Select Project settings.
InGeneraltab, scroll down the page and search for the following items:
{
"apiKey": " project api key ",
"authDomain": " project authDomain ",
"databaseURL": " project databaseURL ",
"storageBucket": " project storageBucket "
}
*Note: If "databaseURL": " your project databaseURL "does not appear, refresh the page and wait a few seconds.
Replace these values inside the db.py file:
class LogData:
def __init__(self):
self.config = {
"apiKey": " project api key ",
"authDomain": " project authDomain ",
"databaseURL": " project databaseURL ",
"storageBucket": " project storageBucket ",
}
From now on, your project is created, with a database connected.It still lacks the configuration of the rules of access to the database.
Click on Realtime Databaseat the left side of the console and choose Rulestab.
Edit the rules to:
{
"rules": {
"users":{
"$uid": {
// Allow only authenticated content owners access to their data
".read":"auth != null && auth.uid == $uid",
".write":"auth != null && auth.uid == $uid"
}
},
"issues":{
".read":"auth != null",
".write":"auth != null"
},
"requests":{
".read":"auth != null",
".write":"auth != null"
},
"requests_historic":{
".read":"auth != null",
".write":"auth != null"
},
"admin":{
// Allow only authenticated admin access to data
// set the email from de admin user'
".read":"auth != null && auth.token.email == '[email protected]' ",
".write":"auth != null && auth.token.email == '[email protected]' "
}
}
}
Note: To configure the app admin, change the auth.token.email == '[email protected]' from read and write to the email that will be the admin created in Authentication.**
For more information about firebase rules, see: https://firebase.google.com/docs/database/security
Your application is ready to run!
On this screen, the user points to which category of problem he requires assistance and details of what happened.
Here, users can follow the progress of their requests
In this part, the administrator can enter new issues, view the correct entry in the issues list, and do a test submission to make sure everything is working.
In this area, the administrator can see the requests and as he solves the problems, he can remove them from the queue. The database is automatically updated and users can follow the queue in real time.
To assist in decision making, there is an area with problem statistics. Thus, it is possible to evaluate recurring problems, assess costs and prevent future problems.
KivyMd
- See documentation at https://kivymd.readthedocs.io
Kivy
- See documentation at https://kivy.org/doc/stable/
KivyMD and kivy are released under the terms of the MIT License.