University · Information systemCase study

CineMates20: one system, two clients.

An information system for movie fans, combining a mobile application for end users with a desktop client for administrators. My contribution covered the entire backend component and the technical and project documentation.

Back to portfolio

University projectBackend + documentation

Reconstructed mock-up of the CineMates20 mobile Home screen

Mock-up reconstructed from the project documentation; it is not a screenshot of a currently running environment.

2 clientsMobile + desktop

1 backendShared services

End-to-endBackend + documentation

01 / Context

One system, two user experiences.

CineMates20 is an information system for movie fans. The project combines a mobile application for end users with a desktop client for administrators, bringing together content discovery, reviews and community-related features.

Mobile client · Android

Discovery and community

The mobile application lets users search for movies, celebrities and profiles, browse details and reviews, create personal lists and interact with the community.

AndroidJavaMVPRetrofit

Desktop client · Administration

Management and moderation

The desktop client supports administrators in reviewing and handling reports and recommending films to users.

JavaJavaFX

02 / Architecture

Keeping clients separate from services.

The project documentation describes a layered architecture: clients communicate with the backend through APIs, while the backend handles access to persisted data. This separation provides a shared server-side layer for two different interfaces.

01 · ClientAndroid mobileJava · MVP

02 · ServicesAPI + BackendPHP · Apache

03 · DataDatabaseMySQL

Desktop admin · Java / JavaFXRetrofitAWS EC2 · S3 · RDS

High-level logical diagram reconstructed from the CineMates20 documentation. AWS services are listed as documented platforms; no unverified service-to-flow mapping is implied.

This page describes the stack documented for the university project. It does not verify the current availability of any service or infrastructure.

03 / Contribution

My contribution: backend and documentation.

My work focused on the server-side component and the technical and project documentation describing the overall system and the relationship between clients and services.

Personal responsibility

I handled the entire Backend component.

My contribution covered the project's backend and its technical and project documentation. The two client applications — mobile and desktop — are presented as part of the team's overall work, without attributing their user-interface development to me.

BackendAPIMySQLTechnical documentationProject documentation

04 / Technical summary

Documented technologies.

A stack combining Java clients, PHP server services and MySQL persistence, with AWS services listed in the project documentation.

Backend and data

Server component

PHP, Apache and MySQL form the server stack described in the project materials. The backend is the shared layer between the mobile and desktop applications.

PHPApacheMySQL

Clients and integration

Applications

Android with Java and the MVP pattern for the mobile client; Java and JavaFX for the administrative desktop application. Retrofit is among the technologies documented for the client layer.

AndroidJavaMVPJavaFXRetrofitAWS

For security, this case study does not include credentials, API keys, configuration files, service addresses or authentication details.