diff --git a/README.md b/README.md index 7952cc8d7c4df5603cffafa5f9cc9c86551d9d48..bbe55770c08a0c2f8906430d1c51e95605e395ca 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,50 @@ -# IF3210-2024-Android-ATM +# Tugas Besar Android IF3210 2023_2024 +## Aplikasi BondoMan +### Deskripsi Aplikasi +BondoMan adalah aplikasi manajemen keuangan yang dikembangkan untuk membantu Bandung Bondowoso dalam mengelola transaksi pembelian bahan baku pada proyek pembangunan seribu candi. Aplikasi ini memungkinkan pengguna untuk menambahkan, mengubah, dan menghapus transaksi, melihat daftar transaksi yang telah dilakukan, melihat grafik rangkuman transaksi, melakukan scan nota, menyimpan daftar transaksi dalam bentuk file Excel, serta mengirim daftar transaksi melalui email. +### Library yang Digunakan +- Room untuk penyimpanan data transaksi secara offline. +- Retrofit untuk komunikasi dengan server. +- MPAndroidChart untuk membuat grafik rangkuman transaksi. +- Apache POI untuk membuat file Excel. -## Getting started +### Screenshot Aplikasi -To make it easy for you to get started with GitLab, here's a list of recommended next steps. + +#### Splash Screen -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! + +#### Login Screen -## Add your files + +#### TransactionList Screen -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: + +#### Input Transaction -``` -cd existing_repo -git remote add origin https://gitlab.informatika.org/snoopidog/if3210-2024-android-atm.git -git branch -M main -git push -uf origin main -``` + +#### Scan Screen -## Integrate with your tools + +#### Twibbon Screen -- [ ] [Set up project integrations](https://gitlab.informatika.org/snoopidog/if3210-2024-android-atm/-/settings/integrations) + +#### Graph Screen -## Collaborate with your team + +#### Settings Screen -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +### Pembagian Kerja Anggota Kelompok +- Muhammad Hanan ( 13521041 ) : Implementasi Scan, Twibbon, Desain Figma, Layouting UI App (25 jam) +- Shidqi Indy Izhari ( 13521041 ) : Implementasi transaksi (CRUD), Eksport XLSX, Intent Gmail, Network Sensin. (30 jam) +- Muhammad Abdul Aziz Ghazali (13521128) : Implementasi login-logout, Header-Navbar, Graf, Check JWT, Broadcast Reciever. (28 jam) -## Test and Deploy +### Jumlah Jam Persiapan dan Pengerjaan +- Anggota 1: 60 jam +- Anggota 2: 60 jam +- Anggota 3: 60 jam -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +--- +Terima kasih telah menggunakan aplikasi BondoMan! 🚀 \ No newline at end of file diff --git a/img/Graph.png b/img/Graph.png new file mode 100644 index 0000000000000000000000000000000000000000..39d4c3d97784c6566135dd6f2b71acc6fb5861e5 Binary files /dev/null and b/img/Graph.png differ diff --git a/img/Login.png b/img/Login.png new file mode 100644 index 0000000000000000000000000000000000000000..c63214bf061d8213f2301ee63af0a6ebd96f9e14 Binary files /dev/null and b/img/Login.png differ diff --git a/img/Scan.png b/img/Scan.png new file mode 100644 index 0000000000000000000000000000000000000000..f7831728a7947ff405f4daa89014c077893ce182 Binary files /dev/null and b/img/Scan.png differ diff --git a/img/Settings.png b/img/Settings.png new file mode 100644 index 0000000000000000000000000000000000000000..99d590de3f2a4cc281d0df0332715e31999efb6c Binary files /dev/null and b/img/Settings.png differ diff --git a/img/SplashScreen.png b/img/SplashScreen.png new file mode 100644 index 0000000000000000000000000000000000000000..a7bc7ec2011db35b4db7b952749569bf76186f23 Binary files /dev/null and b/img/SplashScreen.png differ diff --git a/img/Twibbon.png b/img/Twibbon.png new file mode 100644 index 0000000000000000000000000000000000000000..a5681f7344274d3f91b16d41c579126b779b084e Binary files /dev/null and b/img/Twibbon.png differ diff --git a/img/TxnInput.png b/img/TxnInput.png new file mode 100644 index 0000000000000000000000000000000000000000..a36dfcdc430199db2424e3a23830cb23e0de64b3 Binary files /dev/null and b/img/TxnInput.png differ diff --git a/img/TxnList.png b/img/TxnList.png new file mode 100644 index 0000000000000000000000000000000000000000..42db3a4c1a085faba6e82dfeb9cb66dc5688fbe5 Binary files /dev/null and b/img/TxnList.png differ