\section{Review}
As shown in \autoref{sec:eval}, the proposed framework (see \autoref{sec:solution}) and its implementation (see \autoref{sec:implementation}) deliver what \autoref{sec:scope} asked for regarding the portability aspect.

\subsection{Modular framework}
Given the lean framework core, the development of new analyzers and rendering target is encouraged.
This is backed by the focus on a standalone application instead of extensions to log processing systems struggling with spatial data in the required resolution.

As experienced in \autoref{sec:eval}, a change in the import stage of the processing pipeline is completely unnoticed in the other parts.
The same is true for the addition or modification of analyzering or rendering functionality.

\subsection{Web UI}
With the web interface depicted in \autoref{app:webif}, it is possible for non-expert users to generate pre-defined reports, while researchers can dive into the API of the framework either as preprocessing step or integrated into a larger project.

The web ui also gives direct access to the results for the non-expert users.

\subsection{Results}
Th selection of rendered results in \autoref{img:oebkml}, \ref{img:oebge}, \ref{img:retries}, \ref{img:trackfi}, \ref{img:time} showcases the already possible descriptive analysis capabilities.
\autoref{img:trackfi} features a map view accessible through a browser, which aligns the active screen content of the mobile device with the spatial track.
Selecting the preview image in the timeline below the map, a marker shows the position where this content entered the screen.

\autoref{img:speed} is based on the same analysis result used for \autoref{img:trackfi} with additional postprocessing in between.
This aggregates the speeds of all selected game sessions and calculates the average.
With a baseline reference of 1 kph speed, this plot can hint at game field design issues, e.g. overly long walking passages at high speed.

\section{Outlook}
Considering the future, there are many analysis and rendering targets to come.
As with any kind of software, sooner or later the point may be reached where the proposed architecture fails.
Given the positive result of the integration evaluation, this sure seems pessimistic.
The framework shows some self-debugging feature: Once a log parser is working, analyzers can help to find patterns of log messages to outline the logs structure.

Especially the spatial generalizations presented in \cite{adrienko2011spatial} or the overestimating error accumulation effect of GPS described in \cite{Ranacher_2015} compared to simplified tracks (e.g. following the methodology of \cite{Chen2009TrajectorySM}) are analyses the author looks forward to give a try.