Back to projects[01] / Digital ecosystem for pets

Featured project · Pet Tech

A digital ecosystem connecting pet lovers, pets, and partner businesses.

We designed and built the applications, platforms, services, and integrations that operate Petycard as a connected product ready to evolve.

[STATUS: EVOLVING]
Petycard concept diagram: the administration system and APIs connect the pet lover app, the partner experience, the web platform, and notifications on a shared identity.

Project brief

Scope
Mobile applications, web platform, backend, APIs, integrations, and design system.
Users
Pet lovers, partner businesses, operations staff, and administrators.
Status
Product in evolution.
Participation
Full product creation.

The challenge

Centralize user identities, pet information, partner businesses, services, and operational processes that were distributed across different tools.

The solution

We designed and built a connected ecosystem with mobile applications, web platforms, backend services, APIs, authentication, notifications, and centralized administration.

How it was built

[01]

Pet lover app

The experience brings together identity, profile, pets, preferences, and access to ecosystem flows.

  • Unified session and pet profiles
  • Discovery of partners, branches, categories, and services
  • Confirmations, notifications, and status changes
[02]

Partner experience

Partner surfaces represent businesses, branches, products, services, and operations related to serving pet lovers.

  • Catalogs and services from a controlled operational source
  • Availability, filters, and empty states
  • Operations connected to administration
[03]

Administration and APIs

Administration centralizes permissions, shared entities, business rules, operational states, auditability, and integration contracts.

  • Users, pets, partners, branches, and catalogs
  • Authentication, permissions, traceability, and configuration
  • Authoritative rules for states and sensitive operations
[04]

Cross-surface integration

Different applications work on a common identity, shared types, centralized rules, and consistent contracts.

  • Asynchronous processes, retries, and idempotency
  • Deduplicable events and timeout recovery
  • Responsive design, accessibility, and interface states

Scope and services

  • Product discovery and definition
  • UX/UI and design system
  • Mobile application development
  • Frontend development
  • Backend and APIs
  • Integrations and notifications
  • Architecture and documentation

Process

  1. [01]

    Discovery

    Identify users, flows, shared entities, dependencies, and integration points.

  2. [02]

    Functional definition

    Document features, rules, errors, edge cases, and acceptance criteria.

  3. [03]

    Experience design

    Define visual identity, responsive behavior, accessibility, components, states, and tone.

  4. [04]

    Layered development

    Organize applications, frontend, backend, and integrations with clear responsibilities.

  5. [05]

    Validation and integration

    Review against functional documentation, design, API contracts, and cross-surface compatibility.

  6. [06]

    Deployment and evolution

    Environments, build validation, testing, previews, production, and rollback.

Architecture and technologies

Flutter

Cross-platform mobile applications.

Laravel

Backend, business logic, and APIs.

REST APIs

Contracts between clients, administration, and services.

Firebase

Notifications, synchronization, and complementary services.

Astro, Svelte, and TypeScript

Web surfaces, interactive components, and typed contracts.

Challenges and decisions

Challenge

Avoid isolated products.

Decision

Centralize identity, catalogs, permissions, and states in shared contracts.

Benefit

Each new experience can be added without creating a parallel foundation.

Challenge

Keep mobile, web, and administration consistent.

Decision

Define shared types, envelopes, identifiers, and versioning rules.

Benefit

Lower risk of divergence and silent errors between clients.

Challenge

Operate across mobile networks and asynchronous processes.

Decision

Account for idempotency, timeouts, retries, transient states, and recovery.

Benefit

An action does not duplicate or disappear solely because the client lost the response.

Challenge

Grow without degrading the experience.

Decision

Use feature-based architecture, shared components, documentation, and approval flows.

Benefit

New modules can be added without turning the product into a set of exceptions.

Challenge

Sustain a recognizable brand.

Decision

Use visual tokens, accessibility principles, and shared content guidelines.

Benefit

Users recognize the ecosystem even as their application or role changes.

Outcome

  • Mobile experience, web platforms, backend, and business rules coordinated as one solution.
  • Shared contracts for users, pets, partners, branches, APIs, and notifications.
  • A technical base prepared for new modules without rebuilding the product.
  • Documentation and technical operations to support the ecosystem's evolution.

A connected product needs more than a good interface.

Petycard brings experience, applications, frontend, backend, APIs, and operations together in one solution.

Tell us about your project