EasyBill helps you digitize, catalog and filter your bills and thus is the next step towards a more digitized world. It uses optical character recognition to translate images of your bills into a digital format. This helps you to have a better overview on your spendings.
We used StoryboardThat to create a storyboard for our app:
Our prototype was designed with Figma. It provides an emulated fully working demo.
- Access detailed bill through archive (#3)
- Delete bill (#4)
- Set up database for bills (#8)
- Design suitable app icon (#9)
- Create views according to figma design (#11)
- Establish view navigation (#12)
- Create the initial project structure (#14)
- Create project structure (#15)
- Development pipeline (#16)
- Create archive from database (#17)
- feature/database -> develop (#18)
- development pipeline -> develop (#19)
- feature/design -> develop (#22)
- database refactoring -> develop (#25)
- feature/navigation -> develop (#26)
- experimental/viewmodel -> develop (#31)
- The sprint started with a backlog of 11 tasks
- Different components contributed by different team-members 2.1. Significant overhead in merging/keeping everything in sync
- The implementation has two entities, three DAOs, a converter-class and a singleton for the database
- The implementation constists of five fragments, one of them, the archive, uses a RecyclerView with an Adapter that is bound to the applications ViewModel
- The applications ViewModel offers asynchronous (e.g. non-blocking) access to the database and is available through a factory
- There are Unit-tests for the database module
- The development pipeline is done with travis-ci and integrated into github, enforces sane coding-standards and code-quality through linter-plugin
- Work was done in git-flwo, before merging features/improvements back in a review was needed
- All 11 tasks have been finished ---> Result: a navigable app that has a database filled with some mock data
Result of sprint 2 was a complete rewrite of the application. Part of the rewrite is a new, more polished layout. You can find a small demo video of the current state of the application here:
- Take a picture of a bill (#1)
- Saved a parsed bill (#2)
- Apply filters (#5)
- Apply ordering to the archived bills (#6)
- See statistics (#7)
- Integrate OCR into the App (#10)
- Apply OCR to the picture of a bill (#13)
- Research OCR (#38)
- Add quality/-branches to pipline (#48)
Click here to see all bugs that were fixed
- feature/designAndOrientation -> develop (#43)
- pipeline/tests -> develop (#44)
- quality/ui revamp -> develop (#62)
- feature/take photo -> develop (#65)
- feature/order bills new ui -> develop (#66)
- Started with a sprint backlog of 16 issues
- Different components contributed by different team-members 2.1. Significant overhead in merging/keeping everything in sync
- Rewrote the whole app UI because, the prototype of Sprint 1 wasn't sustainable enough.
- Focus was on implementing statistics and picture taking capabilties (with OCR)
- There are Unit-tests for the database module
- The development pipeline is done with travis-ci and integrated into github, enforces sane coding-standards and code-quality through linter-plugin. Codecoverage gets checked by codecov
- Work was done in git-flwo, before merging features/improvements back in a review was needed