- May 19, 2022
- 1
- 0
- 0
Hi!
I'm starting to develop a form filler application in Android Studio.
I have about 10 types of forms and each of them contains about 8 pages. I thought of developing the application using fragments and for each page of the form, using a fragment. However, I will have about 80 fragments to supply the 10 types of forms and their respective 8 pages and that doesn't sound good to me.
The idea would be to put a forward and backward button at the end of each page, allowing the user to go back and forth between pages. Is my reasoning correct? What other ways can I structure my application?
PS: Each click on forward, I send the filled data to a database in Firebase.
I'm starting to develop a form filler application in Android Studio.
I have about 10 types of forms and each of them contains about 8 pages. I thought of developing the application using fragments and for each page of the form, using a fragment. However, I will have about 80 fragments to supply the 10 types of forms and their respective 8 pages and that doesn't sound good to me.
The idea would be to put a forward and backward button at the end of each page, allowing the user to go back and forth between pages. Is my reasoning correct? What other ways can I structure my application?
PS: Each click on forward, I send the filled data to a database in Firebase.
Facebook
Twitter
Instagram