There are three cooperating layers when developing applications. The first one takes care of data storage, the second one implements business logic of the application itself, and the third displays the content to the user and allows him to interact with it. The first layer is usually the database, while the second layer is found in larger applications that run complex operations with data. This thesis presents the Play framework for developing web applications. It allows designing the presentation layer that implements MVC design pattern. Development of applications in the Play framework follows the principle of convention over configuration. This means that while creating application, one follows Play prescribed pattern, using predefined elements. For example, routing, creating sessions, using ORM tools, etc. Play allows using Java programming language for backend services, Scala to generate frontend (HTML pages) and enables easy integration with JavaScript and CSS. The most known Play users are LinkedIn and Coursera. Application developed using Play consists of four separate units. These are model, controllers, views and accessories. The model consists of Java classes that represent the data from the database in a form suitable for displaying to the user. Controllers implement methods whose results are different views. Views are generated HTML pages that are displayed to the user. Accessories consists of images, CSS and Javascript elements which are used to style the views and process events such as clicking on a button, selecting a value within drop-down menu, etc. Application Redomat was made for this thesis. It allows one to subscribe to a service by taking a number and also administration of servicing those numbers. Development, compiling and running the application is done using SBT. The model that was developed allows one to add or remove a service in the application without rewriting the source code - it suffices to insert or delete a row in the corresponding table in database. All views are generated dynamically using Javascript which generates the model in a structure for presenting the data. The presentation layer implements business logic. The database stores data in a form suitable for creating a model that is displayed to the user. Application Redomat can be used in all institutions where there is a queue for processing. Examples include banks, police departments where personal documents are issued, health and pension insurance offices, and even hospitals and other health centers. At places where the service would be used by a wide range of people, among which there may be many who do not have access to the Internet, we could also use devices that print numbers on a piece of paper. In that case, one application would generate all the numbers to prevent conflicts. Application Redomat would require minor adjustments to work this way. Thus, services would become more accessible and digitalized but still enable users to subscribe for them the old way. In the end my impression of Play is very good. The development of Redomat application using Play framework was somewhat inconvenient considering its incomplete documentation. The documentation is incomplete due to the recent release of a new version of Play. My previous experience in web development includes Microsoft’s ASP.net framework. It follows the principle of convention over configuration and it inspired Play’s evolvement. Therefore, it was quite easy for me to adapt to Play and understand the structure of the application which it defines. On the other hand, the advantage of a well-established development framework such as ASP.net over Play is the more detailed and accurate documentation and more information about it on web. As a Java beginner, the problem I encountered was choosing a library that is compatible with Play and that provides the functionality that was needed. Another lesson I learned was that choosing the right IDE greatly helps with development.