Project archive

Deep technical writeups, not screenshot filler.

These case studies come from the public GitHub body of work — expanded into clear engineering narratives showing decision-making, architecture range, and product thinking.

Contact Ramy Back home

Snapshot

Curated from public GitHub work

Case studies

Skill tracks

Source date

2026-04-14

What writeups cover

Problem framing, role, stack, implementation highlights, and real product direction.

ProductionUpdated Jan 2026

Polymind

A multimodal Telegram assistant orchestrating 50+ models across text, media, and tool-driven workflows.

Problem

Most bot experiences stop at simple prompt-response flows. The goal here was to create a more capable assistant that could route between providers, handle media, and keep the product useful when individual models fail.

Solution

Polymind turns a Telegram interface into a practical AI control surface. The system combines multi-provider model routing, multimodal inputs, fallback behavior, and MCP-aware workflows for a much broader product surface than a single-chatbot demo.

Impact

Delivered a production-facing AI assistant with public adoption, richer multimodal support, and clearer reliability strategies than a single-model bot.

Role

AI systems engineering, bot product design, integration architecture

Stack

PythonTelegram Bot APIGeminiDeepSeekOpenRouterDocker

Key highlights

Orchestrated 50+ models with context-aware selection and fallback behavior.

Supported text, image, document, and voice workflows in one product surface.

Integrated MCP-style tooling concepts for extensible assistant behaviors.

Repository Live demo

LiveUpdated Apr 2026

ExpenseVault

A modern Next.js expense platform for budgets, analytics, goals, realtime updates, and AI-assisted workflows.

Problem

Personal finance tools often ship as dry admin panels. This project focused on making budgeting and expense tracking feel clear, fast, and scalable while still leaving room for AI and realtime support.

Solution

ExpenseVault is the frontend product layer for a fuller financial workflow. It combines authenticated dashboards, analytics, goals, and responsive UI patterns with a stronger product feel than a typical CRUD finance demo.

Impact

Shipped a richer dashboard experience that connects user auth, analytics, and modern interaction patterns into a coherent product shell.

Role

Frontend architecture, UI systems, product layout, feature integration

Stack

Next.js 16React 19TypeScriptFirebaseSupabaseSWRZustand

Key highlights

Structured the app with reusable components, hooks, stores, and typed feature boundaries.

Designed for auth, goals, analytics, and realtime-ready experiences instead of a single expense list.

Applied modern UI patterns that can scale into production-facing dashboards.

Repository Live demo

ProductionUpdated Apr 2026

Expense Tracker API

Production-leaning Spring Boot API for budgeting, analytics, auth, persistence, and media-ready backend workflows.

Problem

Frontend polish only matters if the backend contracts are reliable. This API was built to handle the underlying domain logic for expenses, budgets, goals, and authenticated access without collapsing into controller-heavy code.

Solution

This backend project demonstrates the service and repository discipline needed behind the financial product. The architecture uses Spring Security, persistence, validation, and integration boundaries to support real application behavior.

Impact

Created a backend foundation that supports authenticated financial workflows, analytics endpoints, and future growth into production integrations.

Role

Backend architecture, domain modeling, service/repository structure

Stack

Java 21Spring BootSpring SecurityPostgreSQLFirebase AdminMaven

Key highlights

Separated controllers, services, repositories, models, DTOs, and security concerns.

Integrated persistence, authorization, validation, and external provider boundaries.

Kept the API oriented toward real domain workflows rather than endpoint sprawl.

Repository

LiveUpdated Feb 2026

Minimal Commerce OS

A premium e-commerce frontend balancing minimalist aesthetics, realtime interactivity, and robust full-stack direction.

Problem

Many commerce builds either over-index on visuals or collapse under architectural shortcuts. The aim here was to combine stronger product design with a more serious engineering posture.

Solution

This commerce project explores a more design-conscious product language while still respecting the complexity of a scalable storefront. The repo positions itself around refined visuals, server-side patterns, and richer interaction design.

Impact

Established a more premium commerce foundation that can support richer storytelling, server-driven flows, and polished customer interactions.

Role

Product UI direction, frontend system design, full-stack composition

Stack

Next.js 16TypeScriptTailwind CSSSocket.ioThree.jsGSAP

Key highlights

Pushed a premium visual direction while keeping the architecture App Router aware.

Combined realtime, 3D, and animation tooling without flattening the product hierarchy.

Demonstrated stronger product storytelling than a template commerce scaffold.

Repository Live demo