Skills by Domain
01 / PLATFORM
Mobile Development
Java 17 (Android)
Core Language
Android SDK & Lifecycle
Architecture
OSMDroid & Geolocation
Mapping
XML Layouts & Material UI
Interface
Location Services API
GPS & Sensors
02 / SERVICES
Cloud & Backend
Firebase Authentication
Identity & OAuth
Firebase Realtime Database
Live Sync
Firebase Cloud Storage
Asset Storage
RESTful APIs & JSON
Integration
Google Sign-In API
Verification
03 / SYSTEMS
Systems & Prototyping
System Design & Topology
Architecture
LAN IPC & Sockets
Protocols
C# & Python Scripting
Daemons
HTML5 / Vanilla CSS / JS
Web Consoles
Windows Workstation APIs
System Locking
04 / PRACTICE
CS Core & Workflow
Data Structures & OOP
CS Foundations
Git & GitHub Version Control
Collaboration
Windows & Linux CLI
Environment
Requirements & Testing
Methodology
Clean Code & Documentation
Maintainability
How I Evaluate & Choose Tools
I do not adopt frameworks for the sake of novelty. Every tool in my stack is chosen to satisfy concrete engineering requirements:
- Offline Resilience: In environments with variable connectivity, client software must handle dropped packets gracefully. This is why SafeAlert pairs Firebase Realtime Database with OSMDroid’s local tile caching.
- Lightweight Footprint: For system tools like Library Control, minimal memory and CPU usage on client workstations are non-negotiable requirements to protect user workstations.
- Maintainability: I write code prioritizing explicit types, transparent interfaces, and comprehensive docstrings so that any teammate can jump into the project with minimal onboarding friction.