Artifex

I worked as a Full Stack Developer at Artifex.gg, contributing across backend services and frontend product features to improve the experience for both customers and creators. Artifex is a creator-first marketplace for digital game-development resources, designed to help creators monetize their work while giving customers a safe, modern place to discover, purchase, and manage high-quality assets.

My work focused on building reliable platform foundations (authentication, permissions, secure payments, data integrity) and shipping product-facing improvements (dashboards, marketplace pages, notifications, and creator tools) that reduced friction across the most important user journeys.

Context and goals

Artifex serves two primary user groups with different needs:

• Customers: discover products, buy securely, download files, manage orders, and get support.

• Creators/business users: set up a public profile, list products, track sales and performance, communicate with customers, and manage earnings.

The goal of my contributions was to strengthen core workflows end-to-end:

• Make the platform feel fast and intuitive for everyday users.

• Ensure transactional flows (payments, downloads, subscriptions) are trustworthy and resilient.

• Provide creators with clear dashboards and tools to run their storefronts efficiently.

• Maintain strong security and privacy practices across authentication, data access, and integrations.

My role

I contributed to both backend and frontend development. My responsibilities included:

• Designing and implementing backend functionality that powers core marketplace and dashboard features.

• Integrating and maintaining critical third-party services (payments, file storage, real-time updates, email).

• Building and refining frontend workflows in authenticated areas to improve clarity, usability, and responsiveness.

• Strengthening security posture with validated inputs, secure sessions, controlled access to resources, and safe handling of webhook-driven events.

Key problems

Working on a two-sided marketplace introduces recurring engineering challenges:

• Different experiences for different roles (customer vs creator) without leaking data between them.

• Ensuring that authenticated pages load personalized data quickly and securely.

• Handling edge cases in product ownership and access (buyers vs creators, deleted products, download permissions).

• Creating self-service billing and earnings flows while keeping payment events consistent and auditable.

• Keeping notifications and messaging usable at scale (search, sorting, batch actions, and real-time updates).

Solutions and what I built

1) Authentication and account flows

I contributed to the foundation that enables secure access to the platform:

• End-to-end authentication flows including sign-in, email verification, and password recovery/reset.

• Clear state handling for verification and password reset routes (validation, error handling, and safe redirects).

• Guardrails for authenticated-only pages so unauthorized users are blocked from sensitive views.

Outcome: reduced friction during onboarding and made account recovery a predictable, user-friendly process while maintaining security expectations.

2) Dashboards for customers and creators

A major area of impact was improving dashboard-driven workflows:

Customer-side experiences I helped support:

• A personalized dashboard overview that surfaces relevant account information.

• Orders, tickets, and messages pages that give users a centralized place to manage purchases and support conversations.

Creator/business experiences I helped support:

• Business dashboard pages for managing products, updating profile information, and tracking sales/performance.

• Workflows that encourage profile completeness and provide status feedback (e.g., warnings for missing fields).

Outcome: customers had a clearer “control center” for purchases and support; creators had a more actionable workspace for running their storefront and tracking performance.

3) Marketplace product experience

I supported core marketplace features that shape buying decisions and post-purchase experience:

• Product page behaviors that account for who is viewing (buyer vs creator vs visitor).

• Structured product content sections such as overview, updates/version logs, reviews, and documentation (where applicable).

• Ownership-aware access patterns (for example: buyers can access downloads; creators can see management tools).

Outcome: product pages became more informative and more functional, supporting both conversion (pre-purchase clarity) and satisfaction (post-purchase access and transparency).

4) Notifications and messaging workflows

I contributed to activity and communication features that keep users engaged and informed:

• Notification inbox behaviors with sorting/filtering/search patterns and batch actions (read/unread, archive/unarchive, delete).

• Support for communication workflows that connect customers and creators in-platform.

Outcome: users gained better visibility into platform events and a cleaner way to manage high-volume updates without losing important messages.

5) Billing, payments, and earnings

I helped support systems that must be correct, secure, and auditable:

• Payment and subscription flows integrated with a payments provider (including webhook-driven events).

• Billing and earnings experiences that enable users to view plan status, manage billing details, and track earnings/withdrawals (where applicable).

• Strong validation and security checks around payment events and authenticated access to billing/earnings data.

Outcome: improved trust and usability in the platform’s most sensitive flows—checkout, subscriptions, and earnings management.

6) Discord bot (community + automation)

Alongside the web platform, I also built Artifex’s Discord bot to support the community and streamline routine workflows where users already spend time. The bot complemented Artifex’s broader ecosystem of integrations (including Discord as an auth provider) and helped connect product/community touchpoints with faster, more accessible interactions.​

What I delivered

• Implemented core bot commands and interaction flows (slash commands and/or message-driven actions) to support community needs and internal operations.

• Integrated the bot with Artifex systems where appropriate (for example: linking accounts, surfacing notifications/updates, or routing users to the right support paths).

• Added guardrails around permissions and safety to ensure actions were only available to the right roles (e.g., staff-only commands vs public commands), aligning with the platform’s broader role-based access mindset.​

Why it mattered

• Reduced friction for users by bringing key updates and entry points closer to where the community already engages.

• Improved operational responsiveness by automating repeatable actions and giving the team a lightweight interface for common tasks.

Technical approach

Stack and architecture

I worked in a modern TypeScript-based web stack:

• Frontend: React and Next.js for building responsive UI and supporting server-side rendering where it benefits personalized dashboard experiences.

• Backend: Node.js services with an ORM layer and a database-backed data model for marketplace entities.

• Platform services: containerized workflows for development/CI, file storage integration for digital products, real-time/event integrations for messaging/updates, and email tooling for account and transactional communication.

Security and reliability

Security and trust were treated as core product features:

• Secure session handling and role-based access patterns to protect user and business data.

• Input validation to prevent malformed requests and reduce error-prone edge cases.

• Secure webhook verification and careful processing of external events (especially payments).

• Encrypted transport (HTTPS) and account security support patterns (including 2FA-ready workflows where applicable).

Collaboration and delivery

I worked closely with the core team to deliver improvements across multiple parts of the platform. My day-to-day included implementing features, reviewing edge cases, coordinating changes across backend and frontend, and making pragmatic decisions that balanced speed with stability.

Results (how I present impact)

Because Artifex is a multi-surface platform, my impact is best described in outcomes tied to user journeys:

• Faster, clearer onboarding and account recovery flows.

• More usable dashboards for both customers and creators.

• Better product page functionality with ownership-aware behaviors and richer product transparency.

• Stronger trust in payment-related experiences through secure and consistent billing/earnings handling.

• Improved communication and activity management via notifications and messaging features.