Authorization and registration of the Umoney application Part 1

Development of an international mobile application turnkey (Design + Code) To reduce costs, possibly do not buy a ready-made design 1. General requirements for the project Platform: Cross-platform development on the Flutter framework (one code for iOS and Android). Platform type: Social betting / Gaming disputes on discipline (Peer-to-Peer 도전戰). Executor's task: Full development cycle (UI/UX Design in Figma, frontend, backend server, database, integration of IoT control sensor and payment gateway). Multilingualism: Full support for localization (i18n) and working with multiple currencies. 2. UI/UX Design Requirements A modern, neon-tech interface in dark tones (Dark Mode) is required. Accent colors: Deep graphite (background), bright green (finances, balance), bright red (protection mode on, penalty events). Functionality: Display of 4 main screens in the bottom navigation (Dashboard, Game Rooms, Wallet, Device Settings). Dynamic animations for balance changes and pop-up alerts are needed. 3. Financial architecture (Escrow/Holding/Split) The application is related to holding deposits for compliance with discipline rules. Integration of a payment gateway that supports Split Payments and Holding funds (Stripe Connect for the global market/analogues for local) is critically important. Transaction logic (backend API commands): Replenishment: Users' funds are tied to their account and frozen in the transit (escrow) account of the payment system. They do not go directly to the company's account. SOLO mode: When a trigger event occurs from the IoT sensor during prohibited hours, the backend commands the payment system to transfer a fixed amount (penalty) from the user's transit account to the company's settlement account. GROUP mode (Room): Users form a common pool (for example, 10 people $10). The money is frozen within a specific Game Room. When a trigger event occurs for one of the participants, the amount of their penalty is automatically split: 15% (platform fee) goes to the company's settlement account, and 85% remains within the room's prize pool. After the challenge period ends, the backend automatically distributes the accumulated prize pool among the winners, and the payment system makes an automatic transfer (Payout) to their cards. 4. Cabinet Structure Cabinet 1: "Personal Tracker" (SOLO Mode) Monitoring status indicator (Active/Available/Blocked). Configurator for security time intervals (Time Picker) and settings for penalty trigger costs. Status panel for the external IoT device (sensor battery charge in %, signal level, synchronization status). Cabinet 2: "Game Rooms" (GROUP Mode) Toolkit for creating private rooms (generating invite links/codes for friends) and a list of public global leagues. Leaderboard of participants displaying their current status in real-time, timer until the end of the challenge, and built-in group chat. General section: Multicurrency wallet Display of balance with automatic conversion of local currencies in real-time. Transaction history with a transparent log of deductions, fees, and winnings. 5. Backend and IoT Integration Requirements Stack: Node.js/Python/Go (at the executor's choice, justified). Connection with IoT: Receiving data packets from an external Wi-Fi module. Speed of sending Push notifications (via FCM) to the smartphone upon an event from the sensor – less than 1 second. Anti-fraud logic: The server must analyze the telemetry data transmitted by the built-in accelerometer (accel_x/y/z). If an event occurs with zero change in acceleration axes, the transaction is marked by the system as suspicious (protection against static holding of the sensor), and the user is sent a warning.

If calls are made through a SIM card on an iPhone, it is necessary to automatically transmit information about incoming/outgoing calls to the CRM.

Looking for a developer (or a small team) for long-term collaboration on the TennisBRO project. TennisBRO is a mobile application for tennis enthusiasts. The main goal of the MVP is to simplify the organization of amateur tournaments and the search for playing partners as much as possible. Currently, the project is at the MVP development stage. In the future, there are plans to develop it into a full-fledged ecosystem for the tennis community, but right now only the first version needs to be implemented.Main functionality of the MVP User registration and authorization. Player profile. Creation and conduct of amateur tournaments. Registration of participants for tournaments. Formation of a list of participants. Tournament management by the organizer. Display of the tournament bracket and results. Search for playing partners (singles and doubles matches). Ability to create an open game that other users can join. Push notifications. Built-in chat (if feasible within the MVP).What is important We need exactly the MVP, without unnecessary features. The application should be easy to scale in the future. Clear architecture and quality code are important. Preferably using cross-platform technology (Flutter or React Native), but I am open to your suggestions.Please include in your response What stack you propose for development. Preliminary cost. Implementation timeline. What features are included in the specified cost. Experience in developing similar mobile applications. Examples of completed projects. If additional information or a more detailed technical assignment is needed for evaluation, I am ready to provide it after discussion.