EpiCanvas

Overview

EpiCanvas is the frontend application for EpicTechie, a free and privacy-first web platform providing practical digital tools for everyday document and file workflows. It brings utilities for PDFs, images, OCR, finance, and document processing into a single modern interface, with a longer-term vision of an everyday digital toolbox that includes QR generators, contact card tools, calculators, formatters, and AI-assisted document workflows. The experience is a premium, mobile-first Progressive Web App focused on simplicity, speed, discoverability, and accessibility, without requiring an account to use core tools.

Problem

Everyday document and file-processing tasks often require users to search for individual websites, deal with inconsistent interfaces, encounter unnecessary sign-up requirements, or upload sensitive files without clear privacy expectations. Converting a PDF, extracting text, compressing an image, merging documents, or processing a bank statement is often fragmented across multiple tools. EpicTechie brings those practical utilities together in one accessible platform: useful everyday tools should be fast, free, and privacy-conscious.

Solution

EpiCanvas provides a unified frontend for discovering and using EpicTechie's digital tools, with category navigation and dedicated workflows for PDF conversion, OCR, image processing, financial utilities, and PDF merge, split, compression, booklet arrangement, and signature verification. Users can upload files, monitor processing, view results, and download generated files without an account. EpiCanvas talks to EpiCore for processing, and the frontend and backend are intentionally separated so each can evolve independently.

Architecture

1. 1Next.js App Router
2. 2EpiCanvas frontend application
3. 3Shared tool metadata and types
4. 4EpiCore FastAPI backend
5. 5Temporary file processing
6. 6Generated file and result delivery

Next.js App Router → EpiCanvas frontend application → Shared tool metadata and types → EpiCore FastAPI backend → Temporary file processing → Generated file and result delivery

Responsibilities

• Designed and developed the EpiCanvas frontend application.
• Designed the product experience and information architecture for the EpicTechie tool ecosystem.
• Built responsive, mobile-first interfaces using Next.js and Tailwind CSS.
• Designed tool discovery and category-based navigation.
• Built reusable interfaces for file upload, processing, success, error, and download states.
• Integrated EpiCanvas with EpiCore backend APIs.
• Designed the application for PWA support and modern mobile usage.
• Implemented SEO-oriented page structures and metadata.
• Focused on privacy-conscious file-processing workflows and clear user feedback.
• Designed the frontend architecture to support new tools without major structural changes.

Challenges

• Designing a unified experience for many different types of digital tools.
• Creating reusable UI patterns for workflows with different inputs and outputs.
• Making file-processing workflows simple enough for non-technical users.
• Maintaining a premium interface while keeping the product lightweight and practical.
• Designing mobile-first experiences for tools traditionally used on desktop websites.
• Communicating processing states clearly when operations involve file uploads and backend processing.
• Keeping the frontend architecture extensible as the number of tools grows.
• Maintaining a privacy-first product experience without unnecessary account requirements.

Tech stack

Screenshots

Impact

EpiCanvas provides the primary user experience for EpicTechie, bringing a growing collection of practical digital utilities into a single privacy-first platform. The architecture establishes a foundation for adding new tools while keeping a consistent experience across document, image, OCR, finance, and future everyday workflows. Core tasks are intentionally free to complete without account or subscription barriers.

Lessons learned

• A large collection of utilities benefits from a strong information architecture and consistent interaction patterns.
• Reusable tool interfaces make it easier to expand a platform without creating disconnected user experiences.
• File-processing applications need particularly clear upload, progress, error, and result states.
• Mobile-first design is important even for traditionally desktop-oriented document workflows.
• Separating frontend experiences from backend processing services makes the platform easier to evolve independently.
• Privacy can be treated as a core product principle rather than simply a technical implementation detail.

Future improvements

• Expand the everyday digital tools ecosystem.
• Add QR Code Generator and WiFi QR tools.
• Add Contact Card QR generation.
• Add JSON and developer-oriented formatters.
• Add calculators such as GST and EMI calculators.
• Expand AI-assisted document workflows.
• Improve tool discovery and personalization without requiring user accounts.
• Expand PWA capabilities and offline-friendly experiences where applicable.
• Continue improving accessibility, performance, and mobile usability.