I am looking for developer who would develop application designed in the image (inside attachments).
Application is fully offline.
Calendar, expect to use [login to view URL]
Charts, expect to use [login to view URL]
Local persistence data, (I was thinking about H2 relational db, complete db scheme in the attachments)
Basic idea is described on the image, but more detailed in consisted document will be after the deal (number of screens stay unchanged)
+ local database defined table layout. That so is well defined what I expect to be done.
Example of screen description.
User sees all items defined by screen 11.
List is scrollable by finger movement, order alphabetical.
When user clicks "-" on the item number is decremented but no more than 0.
When user clicks "+" on the item number is incremented, maximum number is 99.
Clicking on button "finish" goes to screen 3, where all items with value higher than 0 will be listed.
User can see complete order done in screen 2.
Before every item list visible is icon of the item.
(Space between sum, and buttons is irrelevant but should be at the bottom of the screen)
In case list is too long, list should be visible, but price and buttons should be fixed (always visible)
Ordered items are sorted alphabetically, first row contains name, second number of ordered items, third price per single item, and forth price*amount.
At the bottom of the screen is visible separating line and under it price sum of ordered items.
When user clicks button "Accept" order is saved to database, and show is screen 4.
When user clicks button "Back" screen goes to 2, with previously selected items still visible.
Button Accept and Back has to be distinguishable for example, red and green.