Plain language is fine
I translate a business or user problem into a technical system without requiring the client to speak engineering jargon.
Software engineer. Complex systems, explained clearly.
I build software products and approach problems at the level of the whole system: application, network, server, device and real operating conditions. I have worked with Android since 2019 and with computers and programming since the early 1990s.

You do not need to arrive with an architecture diagram or a finished specification. It is more useful to explain what needs to work, what already exists and where the problem is today.
I translate a business or user problem into a technical system without requiring the client to speak engineering jargon.
If a problem lives between the mobile app, API, network and device, it cannot be solved reliably by looking at only one layer.
Legacy, an unfamiliar project, an unstable integration or a hard-to-reproduce bug is a reason to understand the system first — not to rewrite everything by default.
The interest in software started long before mobile platforms. The habit that stayed is simple: do not stop at the visible symptom — understand how the system works underneath.
Mikrosha, BK, Elektronika, Yamaha and ZX Spectrum. The Spectrum became the point where programming and computer internals turned into a systematic interest.
Working with a Kempston Joystick required exploring I/O ports directly, while arbitrary-area fill had to be implemented without a ready-made language function.
Pascal, Delphi, Turbo Basic, some Assembler, JavaScript and PHP, together with practical computer hardware work up to complex laptop motherboard repair.
Mobile apps, video surveillance, intercom systems, SIP/VoIP, server APIs, authentication, networking scenarios and device interaction.
A project that brings this experience together around custom software development — from a clear user scenario to a complex engineering system.
If a client only needs the outcome, this section can be skipped. For a developer, CTO or engineer, here are the concrete details.
Kotlin, Java, Jetpack Compose, Android SDK, Material 3, lifecycle, background behavior and UI state.
Coroutines, Flow, dependency injection, layer boundaries, integration isolation, state management and regression control.
REST API, OkHttp, WebSocket, JSON, OAuth 2.0 / OIDC / PKCE, error handling, reconnect and diagnostics.
SIP telephony, Linphone, account registration, incoming calls, audio/video scenarios and real network constraints.
PHP, HTML, CSS, JavaScript, focused web services, bots, backend integrations and operational interfaces.
Git, Linux, Windows Server, Apache, Nginx, reverse proxy, SSL, CI/CD and network services.
Through Deventra you can commission a mobile app, Windows software, web/backend, a website, system software, hardware integration or automation. This page explains where the engineering approach behind the project comes from.