Mobile Commerce Case Study

Alla Vostra

Flagship full stack mobile commerce app

Alla Vostra is a native commerce system focused on polished ordering, multi-payment checkout, server-validated order logic, transactional messaging, and production-minded store delivery.

React Native / Expo 54Stripe + PayPal checkoutServerless commerce backendEAS / Play Store release

Contact Dev

Full-StackUI/UXF-EndB-EndRelease

PlatformsAndiOSWeb

400Quality GitHub Commits

200Real-Time Project Worklogs

2Storefront Releases

1Website

Overview

Alla Vostra Play Store feature graphic — Play Store 1

Alla Vostra turns a boutique grazing-board menu into a native ordering product: customers choose boards, enter delivery and contact details, pay through the best available payment rail, and receive confirmation through backend messaging.

My role covered the app experience end to end: mobile UI implementation, front-end architecture, backend-connected purchase flows, server-owned order validation, PayPal and Stripe coordination, transactional messaging, emulator and device QA, native build setup, and release-focused iteration.

Alla Vostra Play Store screenshot 2 — Play Store 2

Alla Vostra Play Store screenshot 4 — Play Store 3

Alla Vostra Play Store screenshot 5 — Play Store 4

Scope

Scope and Ownership

Mobile Frontend

React Native, Expo 54, and Expo Router implementation for the native ordering app, screen composition, navigation flow, and responsive mobile polish.

Backend / Server Logic

Node.js and Vercel serverless commerce routes for payment sheet creation, PayPal orders, Stripe webhooks, contact messages, and server-owned order validation.

Payments

Stripe card checkout, Google Pay, Apple Pay, and PayPal redirect/capture flows with platform-specific availability checks.

Messaging

Postmark-powered order confirmations after verified payment events plus backend-routed contact form messages with safe reply handling.

QA and Release

Android emulator testing, EAS development/preview/playTest/production profiles, native dev-client setup, TestFlight configuration, and Play Store readiness work.

Product

Core Features

Board Ordering

Customers browse curated grazing boards, adjust quantities, and move selections into a real checkout path.

Local Delivery Flow

Recipient details, contact info, delivery date/time, and Florida service-area checks keep ordering tied to fulfillment.

Multi-Payment Checkout

Card, Google Pay, Apple Pay, and PayPal options are selected from the same checkout experience.

Trusted Order Totals

The server owns catalog prices, delivery fees, tax, quantity limits, and delivery validation before payment begins.

Order and Inquiry Messaging

Purchase confirmations and contact form inquiries route through backend Postmark workflows.

Release-Ready Native App

Versioned Android builds, store assets, native env flags, and EAS profiles support testing through release.

UX Product Flow

Stage 01

Tutorial

This tutorial stage will outline the guided first-use walkthrough.

Browse Grazingboards

Pick Your Quantity

Stage 02

Browse

The browsing surfaces keep the brand, product catalog, company story, inquiry path, and shop entry consistent across Android Small and Large.

Home Screen

Products Screen

Stage 03

SHOP

The shop entry screen bridges browse intent into item selection across Android Small and Large.

Shop Screen

Stage 04

Cart

Cart states were treated as part of the purchase path, with empty and filled moments both needing clear feedback.

Products Overlay

Empty Cart Overlay

Stage 05

Checkout

Checkout details break the purchase path into focused, readable steps instead of one overloaded form.

Contact Input Overlay

Address Input Overlay

Stage 06

Confirmation

The final state closes the loop with a clear success moment tied to the real checkout outcome.

Order Confirmation Overlay

Order Placed Prompt

Architecture

Architecture and Stack

Mobile App

React Native ordering UI

Vercel API

Validated commerce routes

Payment Rails

Stripe, wallets, PayPal

Messaging

Postmark confirmations

Store Builds

EAS, Play Store, TestFlight

01Native App Shell

React Native 0.81, React 19, Expo 54, Expo Router 6, native navigation handling, and bundled app assets.

02Commerce Backend

Vercel serverless routes for health checks, Stripe payment sheets, PayPal order creation/capture, webhooks, and contact messages.

03Order Authority

Backend pricing, tax, delivery fee, quantity, contact, delivery, and Florida service-area validation before payment creation.

04Payment Orchestration

Stripe PaymentIntents cover cards, Google Pay, and Apple Pay; PayPal uses server-created orders and app deep-link return handling.

05Messaging and Release

Postmark handles confirmations and contact inquiries while EAS profiles support native testing, Play Store packaging, and TestFlight configuration.

The project was implemented as an Expo mobile client backed by serverless commerce routes. The app owns the interaction layer, while the backend owns pricing, delivery rules, payment creation, webhooks, PayPal capture, and Postmark messaging. That split kept secrets out of the app and made checkout behavior easier to test across native build targets.

App

React Native 0.81.5React 19.1Expo 54Expo Router 6

Commerce API

Node.jsVercel RoutesServer TotalsStripe Webhooks

Payments

Stripe RN 0.50.3PaymentIntentsWallet PayPayPal REST

Messaging

PostmarkOrder EmailsContact Routing

Release / QA

EAS ProfilesAndroid StudioPlay Store AABTestFlight

Execution

Build Execution

Server-Owned Commerce Rules

The app sends order intent, while the backend owns product prices, delivery fee, tax, quantity limits, and Florida-only delivery validation before any payment is created.

Multi-Rail Payment Boundaries

Stripe card, Google Pay, Apple Pay, and PayPal each have distinct platform and configuration requirements, so the app validates the selected rail before starting checkout.

Backend-Only Messaging Secrets

Postmark delivery is handled through server routes and payment webhooks, keeping email credentials out of the mobile runtime.

Native Build Separation

Development builds can disable Apple Pay entitlement requirements, while preview, playTest, TestFlight, and production profiles keep release paths explicit.

Release-Oriented QA

Android layout, payment readiness, store assets, app versioning, and production bundle behavior were checked against practical release conditions.

Release Readiness

Alla Vostra was not treated as a static concept piece. The work included Android-focused QA, app version 1.0.3 packaging, production AAB preparation, native dev-client testing, TestFlight configuration, and build profiles aimed at real release conditions.

Android v1.0.3Multi-Size Android QAEAS Build ProfilesTestFlight ConfigStripe Live + WebhooksNative Wallet ChecksPayPal Sandbox/LivePostmark MessagingPlay Store AAB

Timeline

Responsive Prototype to Mobile Architecture

The project moved from an interface direction into a React Native, Expo 54, and Expo Router structure built for real mobile ordering paths.

Server-Owned Checkout Logic

Backend work established validated order totals, Stripe payment sheets, delivery constraints, webhook confirmation paths, and safe messaging boundaries.

Multi-Payment Expansion

Checkout grew beyond card payments into Google Pay, Apple Pay, and PayPal, with native/runtime checks for each path.

Native Testing and Store Builds

EAS profiles, Android versioning, Play Store bundle preparation, TestFlight configuration, and free-account iOS development testing were separated into explicit build paths.

Full stack mobile work

Interested in this kind of build?

This project reflects the kind of work I want to keep doing: polished mobile interfaces, server-owned commerce logic, multi-payment integrations, careful release prep, and product decisions that hold up outside of mockups.

GitHub Contact Dev