Skip to content
Back to Mobile Apps
Surplus Food App · TestFlight beta

Shijoje

A mobile beta connecting businesses with surplus food to people who can reserve it free of charge for local pickup.

PRCONNECT PRODUCT
SHIJOJE
Mobile product experience
Surplus Food App
Collection
Mobile Apps
Availability
TestFlight beta
Platforms
iOS beta · Android-ready
Scope
4 disciplines
01 · The challenge

What the product needed to solve

Surplus food needs a fast, trustworthy route from a donating business to a nearby person, with clear timing, allergen information and pickup accountability.

02 · The approach

How PRCONNECT shaped it

PRCONNECT designed a mobile reservation flow for local discovery, pickup windows and one-time codes, alongside business, privacy and food-safety controls.

03 · Product capabilities

The useful parts of the system

01

Nearby offers

Available surplus food can be discovered through a mobile-first local flow.

02

Pickup reservation

Time windows and one-time codes make collection clearer.

03

Safety context

Allergen declarations and reporting are built into the product model.

Case study record

The product reasoning behind Shijoje.

A closer account of the audience, operating constraint and decisions represented by this public project page.

Shijoje explores a local reservation flow that connects businesses with surplus food to people who can collect it free of charge. The challenge is operational as well as visual: availability changes quickly, pickup windows matter and both sides need enough information to complete the hand-off safely and respectfully.

The beta direction includes local discovery, reservation, one-time pickup codes and business controls. Allergen context and reporting are visible because a food-sharing product cannot treat safety as a footnote. Shijoje is labelled as a TestFlight beta and Android-ready direction, not as a claim of public scale, guaranteed food availability or a completed Android store release.

01

Show what is actually available

Offers need quantity, timing and pickup context so people can decide quickly without assuming surplus stock will remain available.

02

Make the hand-off verifiable

A reservation and one-time code can give the business and collector a clearer shared state at pickup without creating a complex transaction.

03

Keep safety information close

Allergen declarations, business responsibility and reporting paths belong with the offer and reservation journey rather than in an unseen policy page.

Scope & evidence

What this page documents.

The recorded scope connects Product concept, Mobile UX/UI, Reservation flow, Trust and safety design for iOS beta, Android-ready, Mobile. The current public status is “TestFlight beta”. These labels describe the work and delivery stage represented here; they are not a substitute for a production audit of the linked product.

PRCONNECT does not publish private customer data, confidential architecture, revenue, adoption or conversion figures on this page. Where no verified result is shown, the case study explains the problem, product direction and delivered or prepared capabilities without inventing an outcome.

A team evaluating a similar surplus food app should use this record as decision context rather than a fixed package. The capabilities described here—nearby offers, pickup reservation, safety context—were shaped around this product’s audience, constraints and delivery stage. A new brief should confirm its own users, content or data ownership, integrations, permissions, accessibility, measurement and support model before copying an interface or choosing a stack. That review is what turns a visual reference into a system the organisation can operate responsibly after launch.

Questions about the work

Clear answers, including the project boundaries.

Is food purchased through Shijoje?

The documented beta model is for free reservation and local pickup of surplus food. If payments or delivery were introduced later, the product, legal and operational scope would change and require a separate review.

Who is responsible for the food information?

A production model needs the donating business to provide accurate item, allergen, timing and pickup information. The platform can structure and display that context, but it does not replace the responsibilities of the food operator.

What should be tested during beta?

Important checks include offer accuracy, reservation expiry, no-shows, pickup verification, reporting, accessibility and how quickly businesses can update stock. A local pilot is the right place to validate these operational assumptions before wider release.

Related work

More from Mobile Apps.

View collection
Your project

Start with the outcome that needs to change.

We will help map the product, workflow and technical delivery required to move it forward.

Start a project