Hi, I'm NimaTHE DIGITAL ALCHEMIST
I build digital products that make an impact. From concept to launch, I craft experiences that users love.
const developer = {
name: "Nima",
skills: [
"React", "Next.js",
"Node.js", "AI"
],
available: true
}
// Currently building
// the next big thing 🚀What I Do
Web Development
Modern, performant web applications built with the latest technologies.
Mobile Development
Cross-platform mobile apps that deliver native-quality experiences.
Technical Consulting
Strategic guidance to help your team make the right technology decisions.
SaaS Products
Full-cycle SaaS development from idea to scalable product.
Impact by Numbers
Featured
Featured Projects
Building a Scalable Bike Sharing Platform (500K Users)
<h2>🚲 Dockless Bike Sharing Platform (500K+ Users)</h2><h3>🟢 Executive Summary</h3><p>Designed and built a full-stack dockless bike-sharing platform, enabling over 500,000 users to rent bikes anywhere in the city.</p><p>Led architecture and product decisions across mobile, backend, and IoT systems, delivering a scalable, real-time platform with payment, geofencing, and smart lock integration.</p><h3>🟡 Problem & Constraints</h3><p>When I joined, the system was:</p><ul><li><p>Station-based (no free-floating)</p></li><li><p>No customer-facing app</p></li><li><p>IoT locks unreliable and dependent on SMS-triggered heartbeats</p></li><li><p>High risk of theft and misuse</p></li><li><p>Payment infrastructure constrained to local providers</p></li></ul><p>👉 The goal was to transform this into a <strong>real-time, city-scale mobility platform</strong>.</p><h2>System Architecture for Real-Time IoT Platform</h2><h3>1. Real-time Communication (REST → WebSocket)</h3><ul><li><p>❌ REST required SMS-triggered wake-ups → unreliable & expensive</p></li><li><p>✅ Switched to WebSocket for persistent connection</p></li></ul><p><strong>Trade-off:</strong></p><ul><li><p></p></li></ul><ul><li><p>Real-time control & monitoring</p></li></ul><ul><li><p>− Increased infra complexity & connection management</p></li></ul><h3>2. Unlock Latency Optimization</h3><ul><li><p>Initial unlock latency: ~1800ms (network dependent)</p></li><li><p>Problem: noticeable delay in user experience</p></li></ul><p><strong>Solution:</strong></p><ul><li><p>Introduced Bluetooth fallback for local unlock</p></li></ul><p><strong>Impact:</strong></p><ul><li><p>Reduced perceived latency significantly</p></li><li><p>Improved reliability in poor network conditions</p></li></ul><h3>3. Wallet as a Microservice</h3><ul><li><p>Built wallet as a separate service early</p></li></ul><p><strong>Trade-off:</strong></p><ul><li><p>− Higher initial complexity</p></li><li><p></p></li></ul><ul><li><p>Enabled future scalability (super-app readiness)</p></li></ul><h3>4. Prepaid (Pay-as-you-go) Model</h3><ul><li><p>Users must charge wallet before ride</p></li></ul><p><strong>Trade-off:</strong></p><ul><li><p></p></li></ul><ul><li><p>Reduced fraud risk</p></li></ul><ul><li><p>− Added friction to onboarding</p></li></ul><h3>5. Cross-platform Strategy</h3><ul><li><p>Android → React Native</p></li><li><p>iOS → PWA</p></li></ul><p><strong>Reason:</strong></p><ul><li><p>Faster time-to-market under limited resources</p></li></ul><p></p><h2>WebSocket vs REST in IoT Systems</h2><h2>🟣 System Design Overview</h2><ul><li><p>Backend: Laravel + MySQL</p></li><li><p>API Layer: REST + WebSocket</p></li><li><p>IoT: SIM-enabled locks with solar charging</p></li><li><p>Geo-fencing: OpenStreetMap (point-in-polygon)</p></li></ul><p><strong>Flow:</strong></p><p>User → API → WebSocket → Lock</p><p>Lock → WebSocket → Backend (location, status, battery)</p><h3>🟠 Key Challenges</h3><h3>IoT Reliability</h3><ul><li><p>Locks previously required SMS to re-establish connection</p></li><li><p>Caused delays and operational overhead</p></li></ul><p>👉 Solved by moving to persistent WebSocket connections</p><h3>Identity Verification at Scale</h3><ul><li><p>Manual verification was not scalable</p></li></ul><p><strong>Solution:</strong></p><ul><li><p>OpenCV-based automation (~90% coverage)</p></li><li><p>Government API for validation</p></li></ul><h3>DevOps Scaling (Pet → Cattle problem)</h3><ul><li><p>Early infra treated servers as “pets”</p></li><li><p>Scaling caused instability and operational overhead</p></li></ul><p>👉 Required shift toward more automated and reproducible infrastructure</p><h3>🔴 Impact</h3><ul><li><p>500,000+ users within ~1 year</p></li><li><p>Peak: 800+ rides/day</p></li><li><p>System downtime: ~3%</p></li><li><p>90% automated identity verification</p></li><li><p>Significant reduction in IoT communication delays</p></li></ul><h3>⚫ My Role</h3><ul><li><p>Led a 5-person engineering team (4 backend + myself)</p></li><li><p>Owned:</p><ul><li><p>System architecture</p></li><li><p>Product decisions</p></li><li><p>IoT integration strategy</p></li></ul></li><li><p>Coordinated with remote IoT team (China)</p></li></ul><p></p>
E-commerce Redesign
Complete redesign and performance optimization of a mid-size fashion retailer, resulting in 340% increase in conversions.
What Clients Say
Latest Articles
View All Articles →From Wireframe to Launch: My Full-Stack Workflow
The exact process I use to take a client project from initial wireframe to production in 6-8 weeks.
Next.js 15 Performance: What Actually Moves the Needle
After optimizing dozens of Next.js apps, here are the changes that consistently deliver the biggest performance gains.
Why Your Website Is Costing You Customers
Most business websites lose 50-80% of potential customers due to preventable mistakes. Here's what to fix first.
Let's Collaborate
Let's Work Together
Have a project in mind? I'd love to hear about it.