Growth Infrastructure

My Tech Stack: How I Build Web Apps, Mobile Apps, and Fast Landing Pages

A detailed look at the frameworks, languages, and tools I use to build scalable web applications, native mobile apps, and high-performance landing pages.

The Summary

My core engineering stack is designed to prioritize rendering performance, native capabilities, and deployment scalability. I build full-stack web applications and websites using Next.js hosted globally on Cloudflare Pages. For mobile, I build natively using Kotlin (Jetpack Compose) for Android and Swift for iOS. To build simple landing pages, I use basic HTML, CSS, and Tailwind CSS for sub-second loading speed, and GSAP to implement advanced animations.

1. The Developer Stack

Every tool in my development setup serves a specific platform, performance target, or user experience goal. Click through the interactive diagram below to explore the roles, core attributes, and practical examples for each tech stack node:

My Core Tech Stack

Frameworks & Development Languages

Next.js

Web Apps & Sites
Why I Use It

My go-to framework for building interactive web applications, client websites, and landing pages. Next.js provides unmatched flexibility in terms of modern UI layout design, fast server-side rendering, and versatile deployment options.

Core Attributes
Dynamic web appsFast SSR/SSG renderingModern UI designUniversal deployments
Practical Example

Build a custom developer analytics dashboard using Next.js App Router for sub-millisecond page transitions and data updates.

2. Web Applications & Global Hosting: Next.js & Cloudflare

For any functional web application, client website, or dynamic marketing channel, Next.js is my absolute go-to framework. Next.js offers a perfect balance between modern React components and backend server rendering. It gives you massive flexibility to manage layouts, routes, and API responses all within a single unified project structure. To speed up my frontend build velocity, I rely heavily on modern component libraries like shadcn/ui for clean copy-paste base primitives, and Magic UI or Aceternity UI for highly interactive, pre-animated visual elements built on top of Tailwind CSS and Framer Motion.

When it comes to putting those sites live, I deploy them on Cloudflare Pages. To be completely honest: configuring the builds, serverless routes, and DNS setups at the very beginning can be a massive headache. However, once you overcome that initial setup hurdle and understand Cloudflare's environment settings, it is hands down the easiest, fastest, and most reliable hosting platform you will find on the Internet. It serves assets globally with zero-latency edge delivery and handles traffic spikes without breaking a sweat.

3. Mobile Core: Native Kotlin (Android) & Swift (iOS)

While cross-platform frameworks (like Flutter or React Native) are popular, I prefer building native applications for the best device integration and lag-free UI layouts. I keep my Android and iOS codebases completely separate:

On Android, my language of choice is Kotlin, utilizing Jetpack Compose to write modern, declarative UI layouts. This makes state management and material design integration clean and direct.

On iOS, I write native Swift (incorporating SwiftUI frameworks). Sticking to Swift ensures that iOS apps load instantly, consume minimal battery, and have full access to hardware APIs without requiring custom bridge scripts. It ensures that custom client analytics trackers or booking tools operate with native speed.

4. Optimization & Animation: Tailwind CSS & GSAP

Not every web page needs a complex JavaScript framework. When I need to build basic, simple landing pages, I strip out the heavy React runtimes entirely. Instead, I write simple HTML, CSS, and Tailwind CSS. The main objective here is extreme optimization—minimizing file sizes to ensure pages load instantly even on weak mobile connections. To add custom imagery without adding byte weight, I use vector-based assets from unDraw, and micro-animated icons from libraries like UseAnimations, Lordicon, or Iconscout Free Lottie Animations which provide interactive motion without loading heavy GIFs or video blocks.

However, speed doesn't mean static. To add a premium, state-of-the-art feel, I use the Greensock Animation Platform (GSAP). GSAP is an absolute masterpiece for front-end motion. I look up premium animation concepts on showcase platforms like Awwwards and Godly.website, and then build them custom using GSAP. The advanced, high-performance scroll-driven timelines, micro-animations, and staggered reveal transitions it provides are simply amazing. It makes layouts feel responsive, interactive, and alive without degrading page performance.

Frequently Asked Questions

Why do you choose native mobile over React Native or Flutter?
Native builds in Kotlin and Swift provide the absolute best performance, smaller app bundles, and seamless platform-specific layouts. They allow direct integration with system APIs without the compatibility issues or lag often found in cross-platform bridges.
Is Cloudflare Pages difficult to configure for Next.js?
It can be a configuration headache initially, especially when setting up edge-compatible SSR routes, environment keys, and build assets. However, once configured, its git-integration and global edge cache make it one of the easiest and most reliable deployments available.
Why use simple HTML/CSS for landing pages instead of Next.js?
For a basic single-page landing page, React is often overkill. Using raw HTML and Tailwind CSS eliminates JavaScript bundle weights completely, resulting in much faster load times and better search engine crawlability.
Does GSAP affect page loading speeds?
GSAP is highly optimized, lightweight, and engineered for high frame-rate rendering. Unlike heavy video loops or uncompressed CSS animations, GSAP executes complex timelines efficiently with minimal CPU overhead, making it ideal for maintaining high performance.
Piyush Sachdeva

By Piyush Sachdeva

Founder of Social Masla and Pulse. Author of The Growth Engine.