I am about to write a ticketing application and want to use Sencha Touch for this.
The general work flow of buying a ticket is always the same, but depending on the event / location, additional details might be required from the buyer. For example, one location could provide additional delivery options and thus the client needs to display additional input fields and transmit the data back to the ticketing server in the web.
The information about what kind of additional information is required is stored on the server. This is necessary, because the information can change from one day to another.
My question is whether the following concept makes sense within sencha and what kind of caveats there might be:
I have a standard workflow for buying a ticket that is stored on the mobile application. After each step of the buying process I submit data to the server and sometimes request some data, e.g., available seats. The server will answer my query and also submit what kind of additional information he wants to have in the next step. This "workflow update" consists of a description of a view on some kind of abstraction level. Sencha Touch will then create a new view based on this workflow update and the buyer will enter the information as requested.
Are there any best practices for creating this workflow update, or should I arrange it totally different?
Thanks in advance for taking a look at this.