The problem RemitGuard solves

Foreign workers and international students in Malaysia routinely send part of their earnings home, or receive support money from family abroad: "every month I need to send Mum 150 USDC", "this month send an extra 30 for school fees". This recurring task is harder than it should be:

• It is expensive and slow. The global average remittance cost is around 6.4% of the amount sent; banks specifically average closer to 15%. Cross-border rails are also slow to settle.

• It is easy to lose track of. Repeated transfers to several recipients, changing amounts, and one-off payments (fees, emergencies) pile up with no single view.

• It is a prime target for scams. "Urgent family emergency, send money now" social engineering preys specifically on people who send money to relatives. A person mid-transfer is exactly the wrong moment to be unprotected.

Existing apps solve the sending but not the judgement - nothing sits between "I got a worrying message" and "the money is gone".

Challenges we ran into

• Mobile Compatibility: Initially we targeted full web-hosted development but hit compatibility issues with mobile devices such as Android and iOS environments. Attempting to run as web-app on Android or iOS causes it to crash. To solve this, we pivoted to building and bundling actual APK binaries using Expo Application Services (EAS Build), ensuring native execution directly on target devices rather than relying on a wrapper.

• Google OAuth Redirect: Initializing Google Sign-In to implement SUI zklogin caused URI mismatch errors the moment we moved away from localhost. we resolved this by explicitly configuring authorized origins and callbacks URIs in the Google Cloud Console for both our production web domain and backend endpoints