Roy Wasker

ANDROID · KOTLIN · JETPACK COMPOSE

Hi, I’m Roy.Mobile
Engineer.

From architecture to the interaction in your hand.
I build Android experiences with Kotlin, Jetpack Compose, and a product mindset.

Explore my work View résumé
  • Kotlin
  • Jetpack Compose
  • Multiplatform
rw.PROJECT PREVIEW

ENGINEER’S NOTEBOOK

Ideas.
Built for mobile.

Kotlin. Compose. A little curiosity.
TrendyView on GitHub
MyPasswordsView on GitHub
INTERACTIVE UI STUDY

Currently building at Cellcom TV

A little about me

ARCHITECTURE → STATE → UI

01 The person behind the code

CURIOUS BY NATURE.
ENGINEER BY CRAFT.

I’m Roy Wasker. I build Android experiences where the details of state, navigation and interaction matter.

My experience spans Android mobile and TV, using Kotlin and Jetpack Compose. I think beyond individual screens: how people move through an app, how it responds to their actions, and how its architecture supports a consistent experience.

I’m a Computer Science graduate. In my own projects, I explore shared Android and iOS experiences with Kotlin Multiplatform, local data and backend systems.

Let’s talk
Currently
Android Developer · Cellcom TV
Since
August 2024
Foundation
Computer Science graduate

EXPERIENCE IN PRACTICE

The details behind
a simple experience.

Three principles that shape how I approach Android engineering: clear interactions, explicit state and thoughtful reuse.

  1. ANDROID TV · INTERACTION

    Keep the next action within reach.

    Good navigation makes the next step clear. On Android TV, that means coordinating focus and scrolling so the selected item stays in view. On mobile, it means shaping touch interactions around the same sense of clarity and control.

    The detail that matters: where focus goes next, and whether the viewer can see it.

  2. ANDROID MOBILE · PLAYBACK

    Treat state and actions differently.

    I think about what an interface shows separately from what a user asks it to do. A media player makes this distinction concrete: playback state describes the screen, while pause and seek are actions. Kotlin flows and ViewModels help give each a clear responsibility.

    The detail that matters: a playback command is an action, not just another screen state.

  3. SHARED MODULES · PLATFORM FIT

    Reuse the foundation. Respect the device.

    I look for useful boundaries between shared logic, reusable UI and platform-specific behavior. Core and Compose UI modules can provide a common foundation, while each app adapts navigation and controls to its device.

    The detail that matters: sharing code without assuming every device should behave the same.

Explore these engineering ideas in my personal projects.

02 Selected work

PRODUCTS WITH
A POINT OF VIEW.

Start with two mobile experiences: shared commerce in Trendy and a local Android vault in MyPasswords. Explore the interfaces and the decisions behind them.

More projects & experiments

03 Skills & toolkit

MOBILE FIRST.
BUILT ON SOLID GROUND.

Android, Kotlin and Jetpack Compose are at the heart of my work. A broader toolkit helps me connect the interface to the systems behind it.

Android Core

  • Android
  • Kotlin
  • Jetpack Compose
  • Coroutines

Multi-platform

  • KMP
  • Gradle
  • Firebase

Backend

  • Java
  • Spring Boot
  • REST

Product craft

  • Git
  • Figma
  • Postman