RiseMate — iOS

Overview

RiseMate is an iOS social-app prototype exploring reciprocal skill exchange. Skills people can teach and want to learn shape profile discovery and matching. The SwiftUI client develops that product idea through profile, messaging and community screens. Earlier Kotlin and Flutter clients are preserved as a separate historical archive.

Problem and objectives

People who want to learn a skill and people able to teach it do not always have complementary interests. The product explores a reciprocal approach: make both teaching and learning interests visible, then provide a path from discovering a suitable profile to communicating with that person.

My role

iOS application development focused on SwiftUI screens, feature-based organization and client-service integrations.

Solution approach

The SwiftUI client organizes profiles, discovery, matching and communication into feature-oriented screens. Model and service responsibilities are separated from presentation, with Firebase integrations for identity and data. Experimental calling and AI-related components exist in source but are not presented as accepted live features. A review-branch target-configuration fix enabled an unsigned simulator build.

Architecture flow

Conceptual flow derived from project descriptions; not an application screenshot.

Core components

• Profiles with teaching and learning interests
• Profile discovery and matching flows
• Messaging and community screens
• Experimental calling integration

Technical challenges

• Organizing multiple social features in a coherent client structure
• Distinguishing source presence from verified live behavior
• Checking source-file membership in the Xcode target

Engineering decisions

• Keep the Swift client separate from earlier Kotlin/Flutter implementations
• Separate presentation, model and service responsibilities
• Report simulator builds separately from device and service acceptance

Testing and validation

• On the 7 November 2026 review branch, adding an existing source file to the Xcode target enabled an unsigned arm64 iOS Simulator build.
• Physical devices, live calls, push, Firebase setup and real-user workflows were not tested.

Outcomes

• Fixed a target-configuration issue blocking the review-branch simulator build.
• Documented the Swift client scope and its distinction from the historical mobile archive.

Limitations and current status

• Development prototype; no claim of active users or production service.
• No established automated application test suite was found.
• Calls, push and external-service configuration require separate validation.
• Real profiles, messages, photos and device data are not shared.