Growth Infrastructure

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

A detailed look at the AI tools, frameworks, languages, and automation I use to write code, build scalable web applications and native mobile apps, and ship fast landing pages.

Table of Contents
Quick Navigate:The SummaryThe Categories1. The Developer Stack2. Writing & Versioning Code3. Building the Web: Next.js4. Native Mobile: Kotlin & Swift5. Optimization: Tailwind & GSAP6. Shipping It Live: Cloudflare7. Automation: n8nFrequently Asked Questions

The Summary

My core engineering stack is designed to prioritize rendering performance, native capabilities, and deployment scalability, with AI doing a lot of the heavy lifting. I write and ship code with Claude Code, version everything on GitHub, and build full-stack web applications 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. Behind the scenes, n8n automates the workflows that keep the business running.

The Categories

Before the tool-by-tool breakdown, here is the bigger picture. I group everything I use into a handful of categories based on the job it does, not the tool itself, writing code is a different task from shipping it live, so lumping them together would just be confusing. Here is what each category actually covers:

CategoryWhat It Covers
AI-Assisted DevelopmentWriting and iterating on code quickly, with a human reviewing every change before it ships.
Version ControlWhere every project lives, keeps its full history, and gets reviewed before anything goes live.
Core Framework (Web)Building the actual web apps, client sites, and dashboards people interact with.
UI & StylingGiving pages and apps their visual design, layout, and look.
AnimationAdding motion, transitions, and interactive polish once the basics work.
Native MobileBuilding dedicated Android and iOS apps instead of a cross-platform wrapper.
Hosting & DeploymentGetting a finished project live, and keeping it fast and reliable globally.
Automation & WorkflowsConnecting tools together to run the operations behind the business.
Examples in Action:Every one of these categories has at least one tool behind it. Click through the interactive stack below to see exactly which, and why.

1. The Developer Stack

Every tool in my development setup falls into a clear category, how I write code, how I build it, how I ship it, and how I automate around it. Click through the interactive diagram below to explore the category, core attributes, and a practical example for each tool:

My Core Tech Stack

Frameworks & Development Languages

Claude Code

AI-Assisted Development
Why I Use It

Claude Code is how I actually write software now. Instead of typing every line myself, I work alongside it, describing what I want, reviewing what it builds, and iterating fast. It handles the repetitive scaffolding so I can spend my time on the architecture and product decisions that actually need a human.

Core Attributes
AI pair programmingFaster iterationHandles repetitive codeHuman reviews everything
Practical Example

Build an entire new blog section, components, data, and page wiring, in one sitting by describing the structure and letting Claude Code draft the implementation, then reviewing and refining it.

2. Writing & Versioning Code: Claude Code & GitHub

Before anything gets built, it gets written, and in 2026, I write almost all of my code alongside Claude Code. Rather than typing every line by hand, I describe what I want, review what it drafts, and iterate quickly. This is not "hands-off" coding, I review every change, but it multiplies how much I can build in a day, especially for the repetitive scaffolding that used to eat up most of my time. If you want the deeper story of how AI fits into my daily workflow, I have written about it separately in my AI workflow.

Everything that gets written lands on GitHub. It is where every project lives, where I track the full history of changes, and where code gets reviewed before it ships. GitHub is also the quiet backbone of my entire deployment pipeline, a push to the main branch is the single action that triggers everything downstream, all the way to a live site.

3. Building the Web: Next.js

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.

4. 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.

5. 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.

6. Shipping It Live: Cloudflare

When it comes to putting 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.

The part that makes this genuinely hands-off day to day is the link back to GitHub: Cloudflare Pages watches my repository, and every push to the main branch triggers a fresh build and deploy automatically. I never manually upload a file, I just push code, and a few minutes later it is live.

7. Automation: n8n

Not everything I build is a website. A lot of what actually runs the business happens quietly in the background, and that is where n8n comes in. It lets me connect tools together, CRMs, spreadsheets, Slack, WhatsApp, AI models, without writing and hosting a custom backend for every small workflow.

I use it for things like logging every chatbot conversation to a data table, sending a daily performance recap to Slack, and syncing leads between tools automatically. If code is how I build the product, n8n is how I build the operations around it. For the full breakdown of how I combine it with Claude, see my n8n and Claude automation stack.

Frequently Asked Questions

Do you write all your code by hand?
No, I write and ship almost everything alongside Claude Code. I describe what I want, review what it drafts, and refine it, rather than typing every line manually. It handles repetitive scaffolding fast, but every change is still reviewed by me before it ships.
Why GitHub instead of another version control host?
GitHub is where every one of my projects lives and keeps its full history, and it integrates directly with Cloudflare Pages, a push to the main branch is what triggers an automatic deployment. That tight, reliable integration with the rest of my stack is the main reason I stick with it.
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.
Why use n8n instead of writing custom automation scripts?
n8n lets me connect tools and build workflows visually, without writing and hosting a custom backend for every small automation. It is faster to build, easier to change later, and keeps the operational side of the business running without adding engineering overhead to every new idea.

Official Documentation & Sources

Piyush Sachdeva

By Piyush Sachdeva.

Founder of Social Masla. Creator of Pulse. Best-selling author of The Growth Engine: Beyond AI and Advertising.