RiseMate — iOS
Private SwiftUI iOS prototype exploring profiles, matching and communication around skills people can teach and want to learn.
Mobile & Desktop / Experimental & Archive
RiseMate — Mobile Archive
Private archive preserving earlier Kotlin/Android and Flutter implementations of RiseMate’s skill-exchange idea separately from the current Swift client.
Original code-generated category illustration; not a product screenshot.
Private codebase; this page shares a general technical summary. Source files, real records and organization-specific information remain private.
Overview
A historical archive of earlier RiseMate mobile implementations. Independent Kotlin/Android and Flutter clients preserve product experiments around skill profiles, matching and communication. The Flutter source also contains community and quiz screens. This work is separate from the current Swift client and is not presented as a currently working released product.
My role: Application development on earlier mobile clients, preserving product workflows and platform experiments in an archive.
Core components
- Skill profiles and reciprocal matching flows
- Messaging and group screens
- Community, forum and quiz modules
- Historical product guidance organized by platform
Validation and current status
- The 7 November 2026 audit completed Flutter dependency resolution in a test copy.
- Analysis reported 211 issues; widget-test compilation failed on existing application/API and template-test errors.
- Kotlin builds and physical-device behavior were not validated.
- Not presented as a working product or current release.
- Flutter analysis and test-compilation failures remain.
- Live identity, messaging and calling services were not validated.
- Historical security claims are not independently verified guarantees.
Show additional technical details
Problem and objectives
Describing different platform experiments as one application makes it hard to identify the current client. Historical feature and setup documents can also imply present-day readiness. The aim was to preserve earlier development work while clearly identifying platform boundaries and existing build limitations.
Solution approach
The Kotlin/Android and Flutter applications are described as independent clients, distinct from the current Swift work. Detailed guidance preserves the product context of profiles, matching, chat and community modules. Dependency resolution, analysis and test compilation are reported separately. The archive therefore explains the product and technical learning process without repeating unsupported historical security or release claims.
Architecture flow
- Independent Kotlin/Android application
- Separate Flutter application with feature-oriented screens
- Shared Flutter models, state and service responsibilities
- Archive boundary separating historical code from the current Swift client
Technical challenges
- Older SDK and API usage conflicting with current tooling
- A template widget test diverging from the actual application
- Avoiding presentation of historical features as current acceptance evidence
Engineering decisions
- Treat Kotlin, Flutter and Swift clients as distinct implementations
- Separate major SDK modernization from documentation corrections
- Preserve useful product details in the archive guide
Outcomes
- Clarified the two earlier mobile clients and their distinction from the Swift project.
- Preserved detailed product context while exposing known analysis and build failures.