% Lokální makra patří do hlavního souboru, ne sem.
% Tady je mám výjimečně proto, že chci nechat hlavní soubor bez maker,
% která jsou jen pro tento dokument. Uživatelé si pravděpodobně budou
% hlavní soubor kopírovat do svého dokumentu.

\def\ctustyle{{\tenss CTUstyle}}
\def\ttb{\tt\char`\\} % pro tisk kontrolních sekvencí v tabulkách

\label[Future work and deployment]
\chap{Future work and deployment}

In this chapter, I would talk about the future work and features that will the application have during public release and features planned to be added after release. The next part would be different possibilities with the deployment of the front-end and back-end separately.

\label [Future features]
\sec Future features

Based on the testing I would say the most critical feature missing that needs to be implemented is the redirection to reservation system of the selected cinema. The other features are simply a quality of life improvements like changing the sorting of the screening lists. 

The next big features would come after the initial release. One of the features planned is a cinema visit planner, where you could create an event and invite friends into it. In the screening event, you would have a voting system to help you pick a date of the visit for the group. If we had the ability, a nice thing to have would be that everyone would buy his ticket independently, but the reservation would be organized as a group.

With this feature, a user system needs to be implemented with Google and Facebook integration to make the creation of accounts as simple as possible. The user system was excluded from the initial changes due to the GDPR changes. User Account would give more possibilities with customization within the application and integrated rating system for movies and cinemas.

Also at first, the application will support only Cinemacity and Cinestar chains in Prague to have a soft launch. With expansion across the Czech Republic after release and implementation of new cinema chains.

\break
\label [Fron-end deployment]
\sec Front-end deployment
As front-end being developed for the Apple platform iOS, there is only one way to deploy the application, and that is to make available on the App Store. To make this possible, you have to enroll in the apple developer program [3]. Anyone can enroll the only thing that one needs to do is to pay 99 USD per year get access. Other then this it enables advanced features to be used in the application and the ability to test the application on larger scall to imitate release.
\phantom{somespacesomespacesomespace}
\phantom{somespacesomespacesomespace}
\phantom{somespacesomespacesomespace}
\phantom{somespacesomespacesomespace}
\phantom{somespacesomespacesomespace}
\phantom{somespacesomespacesomespace}
\phantom{somespacesomespacesomespace}


\label [Back-end deployment]
\sec Back-end deployment
Back-end deployment would be split into two. The first being the Python application and the second being the database. There are multiple options how to deploy, but I would narrow the selection down and use only cloud solutions. For the Python application, I would compare two solutions. AWS EC2 instance and Heroku service.

AWS pricing depends on how powerful machine you have allocated and how many as it can dynamically scale based on usage. The pricing [4] would fully depend on the number of users and how well is our application optimized. And we are just allocating a virtual machine, so all the set-up needs to be done by us.

Heroku [5] is a service that simplifies the process of deploying an application. This means you don't have to setup the environment itself and is one point to manage everything. It also has autoscaling capabilities. But the most beneficial feature is you can easily monitor how is your application performing.

For the database, we could also use Heroku which would be the best option if we choose the platform to deploy our application. Or we could use options directly from Mongo called Atlas [6] which support running on multiple nodes to make the database more stable and fail-safe.

\medskip \clabel[Deployment diagram]{Deployment diagram}
\picw=16 cm \cinspic img/deploy.png
\caption/f Deployment diagram
\medskip

