I'm live now. If you see it you can join me. Let's talk Tech!

You can deploy your personal project initially free until you get paying users on Cloudflare Workers. It's possible to deploy backend and frontend but you have to be willing to make some adaptations for the app to be compatible with the cloudflare environment. You get DNS, database, logging and more for free (again until you get paying customers). Later you can migrate to something more professional of stay on the paying services of cloudflare. They also offer many other AI related services.

After a month of building Profit Pilot's web app, I started working on the mobile version to keep both platforms moving in parallel. This is where most projects face a critical decision: 1. Build everything twice (double the time, double the cost) 2. Architect once, deploy everywhere I chose option 2—even with both apps still in active development. My approach: Instead of maintaining two separate codebases, I engineered a unified architecture that powers both platforms simultaneously with enterprise-grade scalability. The architecture: → Turborepo monorepo for lightning-fast builds and intelligent caching → Shared TypeScript types with strict type safety across all packages → Centralized business logic - write once, run everywhere → Platform-optimized auth (secure session cookies for web, JWT with refresh tokens for mobile) → Shared UI component library maximizing code reuse → Real-time sync between platforms using optimistic updates → Automated CI/CD pipeline deploying to both platforms simultaneously → Environment-agnostic API layer with consistent error handling The technical edge: → 70%+ code sharing between platforms → Type-safe API calls with auto-generated clients → Single source of truth for business logic and validation → Consistent user experience across all devices → One security audit, one performance optimization—both platforms benefit Tech stack:Next.js 14 (web) | React Native/Expo (mobile) | Turborepo | MongoDB Atlas | TypeScript | tRPC/REST API | React Query | Zod validation

This is the project I launched. Since it was vibecoded the next step in my strategy for this kind of projects is to migrate it to my own infrastructure since replit was good for the first version (aka MVP) but I want it to mature somewhere else. In this case I want to run it on cloudflare because of the generous free tier and if the project outgrows it then I'll move to the next stage and deploy it on a Kubernetes cluster.

While reviewing the TechCognify website, I noticed something interesting. The entire site was fast ⚡—except the reviews section, which was taking 10–15 seconds to load. Since the frontend was already optimized with Next.js, this immediately pointed to a backend-level bottleneck, not a UI issue. On inspecting the api/reviews endpoint, the root cause became clear: Images were being stored and served directly from the database, instead of an optimized media delivery service. This led to: - Heavy API payloads - Slow response times - A degraded user experience Fix:I refactored the media flow and moved image storage to an optimized external service. Outcome:Instant load times for reviews and consistent performance across the site. Key takeaway:Performance issues often aren’t visible in the UI.They’re the result of early architectural decisions, especially around media and data handling. Frontend optimization helps.Backend decisions define scale. #NextJS #WebPerformance #BackendEngineering #SoftwareArchitecture #TechCognify