1
Вероника
no recommendations
no complaints
Closed
Project title: Simple app
Type of cooperation: Periodic employment
Section: Mobile app development
Prepayment: without prepayment
Payment methods: Cash, Bank transfer, Electronic money
Acceptance of requests: closed
Type of cooperation: Periodic employment
Section: Mobile app development
Prepayment: without prepayment
Payment methods: Cash, Bank transfer, Electronic money
Acceptance of requests: closed
Project description:
We need a working mechanism for simply counting coupons. We are a project that offers to attend St. Petersburg events on discounted tickets. There is a website where the user can take a coupon to attend the event. We need mass events to be conducted through the app. Ie would be such an application, which has 2 types of personal cabinets (?): one for us, the other for the organizers of events. In our - a list of all organizers (with the possibility to add new - just the name) and a list in each organizer of its events with coupons for these events.
The organizer has a list of his events and a list of coupons for each of them.
For example: There is an event "Strawberry Festival", organized by "Funny Gardeners"". We have on the website of agreements with the organizers hangs an invitation to visit the festival of strawberries with a discount on the coupon. User Egor Sobolev takes a coupon (the form for the coupon on the site we have - she asks the user for the name, surname, post and COL_IN NEED BUYS.) User Egor Sobolev took a coupon on the site, filled out the form, the information from the form was transferred to our office and to the organizer's office "Fun gardeners".
Egor came to the festival without any printouts or quark codes, at the entrance he gives his name and surname. He is met by the organizer, who on the app finds in the list of participants of the festival: Yegor Sobolev and opposite him presses the button "Visited" The information that Yegor Sobolev visited the festival was also displayed in our personal office of this festival from this organizer. (synchronized tables)
As a result, the event is over. We have 2 types of list that can be downloaded from the app: Those who visited (like Yegor Sobolev) and those who did not come (but took coupons).
It is good if the table will be able to filter by VISIT / did not visit. The schedule is minimal - logo and background.
We need a working mechanism for simply counting coupons. We are a project that offers to attend St. Petersburg events on discounted tickets. There is a website where the user can take a coupon to attend the event. We need mass events to be conducted through the app. Ie would be such an application, which has 2 types of personal cabinets (?): one for us, the other for the organizers of events. In our - a list of all organizers (with the possibility to add new - just the name) and a list in each organizer of its events with coupons for these events.
The organizer has a list of his events and a list of coupons for each of them.
For example: There is an event "Strawberry Festival", organized by "Funny Gardeners"". We have on the website of agreements with the organizers hangs an invitation to visit the festival of strawberries with a discount on the coupon. User Egor Sobolev takes a coupon (the form for the coupon on the site we have - she asks the user for the name, surname, post and COL_IN NEED BUYS.) User Egor Sobolev took a coupon on the site, filled out the form, the information from the form was transferred to our office and to the organizer's office "Fun gardeners".
Egor came to the festival without any printouts or quark codes, at the entrance he gives his name and surname. He is met by the organizer, who on the app finds in the list of participants of the festival: Yegor Sobolev and opposite him presses the button "Visited" The information that Yegor Sobolev visited the festival was also displayed in our personal office of this festival from this organizer. (synchronized tables)
As a result, the event is over. We have 2 types of list that can be downloaded from the app: Those who visited (like Yegor Sobolev) and those who did not come (but took coupons).
It is good if the table will be able to filter by VISIT / did not visit. The schedule is minimal - logo and background.
