SKIP TO CONTENT
00 /INDEX

Hi, I'm Ridwan Febnur Asri Redinda

Mobile &
Fullstack
Engineer

I build and maintain production mobile and web applications — covering the full development lifecycle, from requirement analysis and technical design to release management and post-production improvements.

SYSTEM STATUS

STATE
available for new projects
BASE
Indonesia · GMT+7
FOCUS
mobile · web · backend
MODE
end-to-end delivery
01 /

ABOUT

Illustrated portrait of Ridwan Febnur Asri Redinda
FIG. 00 — ENGINEER

I'm an engineer with hands-on experience building and maintaining production applications in real-world environments. My core is mobile — scalable, high-performance apps with strong attention to clean architecture, maintainability, and long-term system growth — and I work across the stack, from web frontends to backends and admin platforms.

I've worn multiple hats across the entire build-ship-operate cycle — from scoping requirements and designing architecture to shipping features and maintaining systems after launch. I'm comfortable working across disciplines: product, design, backend, and infrastructure — whatever it takes to move a product from intent to production.

I started on the web — building interfaces, wiring up backends, learning how data moves between a browser and a server. Mobile came next and quickly became my core: the constraints of a pocket-sized device sharpen every decision, and the distance between a thumb tap and a backend response is where software either feels alive or indifferent. But the deeper I built on mobile, the further I was pulled below the surface — data modeling, API design, system architecture — the decisions that outlive any single feature. That's what keeps me working across the stack: the craft of engineering systems that feel straightforward to use because the complexity is handled where it belongs.

  • PROBLEM SOLVER FIRSTunderstand the core problem before the code
  • DESIGN-AWAREbridging the gap between design and implementation
  • PRODUCTION-READYcode that scales in production is the goal
  • CONTINUOUS LEARNINGstaying curious is non-negotiable
02 /

STACK

MOBILE

  • Flutter
  • Dart
  • BLoC
  • Clean Architecture
  • Android & iOS
  • Dependency Injection
  • Offline & Local Storage
  • Biometric Authentication
  • Background Tasks

WEB & BACKEND

  • Next.js
  • React
  • TypeScript
  • Laravel
  • PHP
  • REST API
  • MySQL
  • PostgreSQL
  • Firebase
  • Supabase
  • Auth & RBAC

SHIP & OPERATE

  • Requirement Analysis
  • Play Store Release
  • App Store Release
  • Shorebird OTA
  • CI/CD
  • Push Notifications
  • Analytics
  • Crash Debugging
  • In-App Purchases
03 /

WORK

Selected systems, condensed to what matters: role, impact, and how they were engineered. Open a spec for the full story.

Timefio mobile app — schedule and routine screens
FIG. 01mobile

mobile

Timefio — Schedule & Routine

ROLE
Founder & Mobile Engineer
YEAR
2026 — present
STACK
Flutter · Dart · Cloud Sync · IAP
IMPACT
Solo-built, end to end
STATUS
live on Play Store

Personal productivity app I founded and shipped to the Play Store: schedules, recurring routines, full-screen alarms, productivity recaps, cloud sync, and in-app purchases — bilingual (ID/EN).

LIVE ↗

OVERVIEW

Timefio is my own product — designed, built, monetized, and operated solo. It helps users organize schedules, build recurring routines, and understand daily productivity through reminders, full-screen alarm flows, and recap insights with scoring and streaks. The full product surface is mine: authentication, cloud synchronization, localization (ID/EN), in-app purchases, privacy, and Play Store distribution.

OUTCOME

A complete production mobile product — scheduling workflows, reminder reliability, recap analytics, monetization, and multilingual UX — shipped and operated as a solo founder.

CONTRIBUTIONS

  • End-to-end design and development in Flutter — every screen, every state
  • Flexible scheduling engine with configurable recurrence and full-screen alarm flows
  • Productivity recap: scoring, streaks, and period insights that turn activity into visible progress
  • Full product surface: auth, cloud sync, localization (ID/EN), IAP, and Play Store distribution

CHALLENGES → SOLUTIONS

  • Reliable alarm & notification delivery

    Full-screen alarm interactions with snooze/completion handling and follow-up notifications to reduce missed tasks while respecting user preferences.

  • Turning activity into useful feedback

    Recap and productivity scoring based on completion, consistency, streaks, and time patterns.

Enterprise HRIS mobile app — attendance and HR workflows
FIG. 02enterprise

enterprise

Enterprise HRIS App

ROLE
Mobile Engineer (Flutter)
YEAR
2024 — 2026
TEAM
3+ developers · Agile/Scrum
STACK
Flutter · BLoC · FCM · Shorebird
STATUS
in production (internal)

Production HRIS mobile app for daily employee operations — attendance, leave, overtime, appraisal. I joined at v3 to evolve a live product with a cross-functional team.

LIVE ↗

OVERVIEW

An enterprise HRIS serving real daily employee operations. I worked on the v3 evolution of a live product: refactoring UI across 20+ screens to design-system guidelines, strengthening interconnected HR workflows (attendance, leave, overtime, appraisal, business trips), push-notification handling, and the OTA release lifecycle — all without disrupting active users.

OUTCOME

Sharpened a live enterprise HR product through its v3 cycle — more consistent UX, sturdier workflows, and a faster, lower-risk release loop.

CONTRIBUTIONS

  • UI refactor across 20+ screens — attendance, leave, and overtime modules aligned to design-system guidelines
  • Interconnected HR workflows spanning attendance, leave, overtime, appraisal, and business trips
  • Push-notification handling for real-time HR workflow updates
  • Shorebird OTA release lifecycle — faster iterations without disrupting active users

CHALLENGES → SOLUTIONS

  • Evolving a live production app to v3

    Refactored UI and flows alongside analysts and backend engineers while preserving functionality for existing users.

  • Scalability in a growing codebase

    BLoC state management and dependency injection for clarity, predictability, and long-term maintainability.

Enterprise CRM mobile app — lead management and reporting
FIG. 03enterprise

enterprise

Enterprise CRM App

ROLE
Mobile Engineer (Flutter)
YEAR
2024 — 2026
TEAM
3+ developers · Agile/Scrum
STACK
Flutter · BLoC · Clean Architecture
STATUS
in production (internal)

Mobile CRM built from scratch for field sales teams — lead management, activity tracking, and real-time reporting, delivered in an Agile team.

LIVE ↗

OVERVIEW

A production CRM application I helped build from scratch to support sales teams managing leads, tracking customer interactions, and monitoring performance on the go. I worked closely with business analysts and backend engineers to translate sales requirements into a structured mobile workflow — applying Clean Architecture and BLoC for predictable state management, and managing the Shorebird OTA release pipeline for ongoing production updates.

OUTCOME

Delivered a structured, efficient sales workflow — customer relationships, activities, and performance insights accessible directly from the field.

CONTRIBUTIONS

  • Lead management module — data model, workflow, and UI for field sales teams
  • Sales activity tracking and customer interaction logging
  • Real-time reporting dashboards consumed by field teams
  • Clean Architecture + BLoC across the full feature set for predictable state management

CHALLENGES → SOLUTIONS

  • Translating sales requirements into a structured mobile workflow

    Collaborated closely with business analysts to model lead management, activity tracking, and reporting around how field teams actually work day to day.

  • Consistent state management across a growing feature set

    Applied BLoC with clean architectural boundaries to keep behaviour predictable and the codebase maintainable as features expanded.

  • Reliable deployment and update strategy

    Managed application builds, deployment pipelines, and Shorebird OTA updates, enabling faster iteration and smoother production releases.

Porto Portal mobile app — unified gateway and navigation screens
FIG. 04enterprise

enterprise

Porto Portal App

ROLE
Mobile Engineer (Flutter)
YEAR
2025 — 2026
TEAM
3+ developers · Agile/Scrum
STACK
Flutter · BLoC · Clean Architecture · Shorebird
STATUS
in production (internal)

Enterprise mobile portal serving as a unified access gateway to internal systems across the Porto ecosystem — consolidating multiple services into one authenticated entry point.

LIVE ↗

OVERVIEW

Porto Portal is a centralized mobile gateway built to unify access to internal enterprise systems, simplifying navigation and reducing the need for multiple logins across different tools. I contributed to developing the app from scratch as part of a cross-functional team, working closely with backend engineers and business analysts to design and ship the platform.

OUTCOME

Unified access to several internal services behind a single mobile gateway, simplifying workflow navigation for employees and strengthening consistency across the enterprise mobile ecosystem.

CONTRIBUTIONS

  • Core navigation and access control architecture for the unified gateway
  • Flexible service-integration layer connecting to multiple enterprise back-ends
  • Reusable UI component library and design tokens for cross-module consistency
  • Clean Architecture patterns keeping feature modules isolated and testable
  • Shorebird OTA pipeline — deployment, distribution, and iterative updates across Android and iOS

CHALLENGES → SOLUTIONS

  • Unifying access across multiple internal services

    Designed a flexible navigation and access model that consolidates links to various enterprise back-end services into a single, coherent mobile interface.

  • Maintaining UI consistency across a growing module surface

    Collaborated with UX designers and backend engineers to define reusable components and design tokens, ensuring visual and interaction consistency as modules expanded.

  • Keeping the architecture scalable as integrations multiplied

    Adopted Clean Architecture and BLoC state management to modularize feature sets, making the portal maintainable as new internal services were onboarded.

  • Smooth production rollouts across platforms

    Managed application builds, deployment pipelines, and Shorebird OTA updates, enabling efficient distribution and iterative improvements across Android and iOS.

Academic digital signature system — document signing interface
FIG. 05web

web

Academic Digital Signature System

ROLE
Backend Engineer & System Architect
YEAR
2025
STACK
Laravel · Filament · RSA · SHA-256
IMPACT
Replaced wet signatures in daily ops
STATUS
in production

RSA-based digital signature platform for academic documents — approval workflows, cryptographic signing, and public QR verification. In daily use at the Informatics program of UMT.

LIVE ↗

OVERVIEW

An academic information system where I designed and implemented the digital-signature capability end to end: multi-step document approval, RSA-based cryptographic signing with SHA-256 hashing and encrypted private-key storage, PDF embedding via TCPDF/FPDI, and a public QR verification endpoint that validates authenticity without authentication barriers.

OUTCOME

Replaced manual wet-signature processes for academic documents, cut administrative overhead, and made verifiable digital approval part of daily academic operations.

CONTRIBUTIONS

  • RSA-based digital-signature system — key generation, SHA-256 hashing, and encrypted private-key storage
  • Multi-step document approval workflow with configurable validation rules
  • PDF signing pipeline: signature embedding, QR verification, and tamper detection via TCPDF/FPDI
  • Public verification endpoint — QR-based, no authentication required

CHALLENGES → SOLUTIONS

  • Secure, verifiable signatures

    RSA + SHA-256 with controlled key management and identity validation for authenticity and non-repudiation.

  • PDF integrity after signing

    Processing pipeline embedding signatures and QR codes directly into documents, enabling tamper detection and long-term verification.

  • Public verification without login

    QR-based public endpoint validating authenticity while keeping the system itself secured.

HIMTI UMT mobile app — events and attendance screens
FIG. 06mobile

mobile

HIMTI UMT App

ROLE
Mobile Engineer (solo)
YEAR
2024 — 2025
STACK
Flutter · Firebase · Shorebird · CI/CD
IMPACT
Primary platform for the association
STATUS
live on Play Store

Official Android app of the student association — events, member engagement, and authenticated attendance tracking. Architected solo and shipped to the Play Store with OTA updates.

LIVE ↗

OVERVIEW

The official app for the Informatics student association at UMT, centralizing event information, member engagement, and attendance in one platform. Built from scratch solo: modular architecture, member-only authenticated check-ins, environment-based dev/prod configuration, and Shorebird OTA updates to cut release friction.

OUTCOME

Became the association's primary digital platform for communication and event attendance — improving participation tracking and information distribution on a maintainable foundation.

CONTRIBUTIONS

  • Architected and developed the entire app from scratch in Flutter
  • Implemented event management with real-time updates
  • Built member-only attendance with secure authentication
  • Integrated Shorebird OTA updates and environment-based config

CHALLENGES → SOLUTIONS

  • Maintainable architecture as a solo developer

    Clean, modular patterns keeping the codebase scalable as features grew.

  • Frequent updates without user disruption

    Shorebird over-the-air updates, reducing dependency on full Play Store releases.

ARCHIVE / REGISTRY

Additional projects, listed in brief
NOPROJECTYEARLINK
07Enterprise Sales App2024 - 2026LIVE ↗
08Enterprise Customer App2024 - 2026LIVE ↗
09HIMTI LMS2024 - 2025LIVE ↗
04 /

CONTACT

Open for new
projects.

I'm open to opportunities in mobile product development, fullstack engineering, and long-term collaboration with distributed or cross-functional teams. The quickest way to reach me is email.