Porting the application from Android to iOS (Flutter)

It is necessary to develop an application for App Store. There is a ready Android application and a reference. I am attaching 5 screenshots of a similar application from the App Store as a reference to the project. They are needed to understand the structure of the application, screens, and required functionality. It is not necessary to fully copy the application — the reference is used as a guideline for UX, logic of operation, and set of features.Main functionality List of partner companies (logo, rate, amount, term, rating, transition button). Credit calculator. Currency converter. Payment reminders. Push notifications. Settings screen and informational pages.Admin panel A simple admin panel is needed so that without releasing a new version of the application, it would be possible to: Change the order of offers. Add, edit, and delete companies. Change partner links. Hide or show offers. Send Push notifications.Additional Integration of AppsFlyer for analytics. Assistance with publishing the application in the App Store. Assistance with registering an Apple Developer account for a Ukrainian company. After registration, Apple requested confirmation of identity, connection with the company, and documents of the legal entity. The documents for the company are available; a specialist is needed to help understand Apple's requirements and complete the account registration.What we would like to see in the response Examples of your iOS applications. Experience in publishing applications in the App Store. Experience in integrating AppsFlyer. Will you be able to help with Apple Developer? Estimated cost of development. Estimated timelines for development. Budget and timelines are negotiable.

We are looking for an experienced system architect / Backend engineer (Node.js/Python/Go) to design technical documentation and create the first functional prototype of the MVP mobile application with LLM (Large Language Models) integration. The project aims to create an interactive AI assistant that analyzes the user's textual and visual content (symbols, event photos) in real-time based on the logic of a game quest and narrative ("mirror of reality"). Specific stage of work: Stage 1: Designing the technical architecture, developing the database schema, and creating a working prototype of the AI assistant logic (Core AI Router). Clear list of tasks and boundaries of responsibility: System architecture design: Creating an architectural scheme for the interaction of the client (Mobile App), server (Backend), and external APIs (OpenAI / Anthropic / mobile camera). Database design: Developing a database schema (PostgreSQL / MongoDB) for storing user profiles, request logs, game coin balances, and AI dialogue context. Content Processing Logic (AI Router): Developing a backend module that receives photos/text from the user, forms a system prompt (Persona: Cheshire AI), and returns a structured response (JSON). Tokenomics Module (Game Logic): Implementing a basic algorithm for awarding in-game points/coins to the user's balance after each successful session/validation of insight. Technical requirements (Technology stack): Backend: Node.js (TypeScript) / Python (FastAPI). AI Integration: OpenAI API (GPT-4o) or analogs with Vision support (for image analysis). Database: PostgreSQL (for users and balance) + Redis (for storing sessions and chat context). Documentation: Swagger/OpenAPI for describing endpoints. Expected result (Acceptance criteria): Architecture Document (PDF/Notion): UML diagrams, database schema, API endpoint descriptions, and prompting logic. Working MVP module (GitHub Repository): Clean backend server code, ready for deployment in Docker. Demonstration: A working API that successfully accepts a test photo/situation description, processes it through LLM in the assigned role of "Cheshire," returns an interpretation, and correctly credits the game coin to the balance in the database. Execution timeline: 14–21 days from the moment of approval of the executor.

We are a DTC wellness brand, selling dietary supplements to the US market via subscription, and the app serves as an assistant that gets to know the customer better, collects their data for further mailing, which will remind them to take the supplements (AM/PM), mark intake in the calendar, and show progress. The app is gamified with achievements, personalized push notifications with compliments for each day, and pleasant predictions (like in fortune cookies). Backend / data — Firebase 1. OnboardingThe user opens the app — the first screen with the SHE·8 logo, a photo of a girl, and the text “Your daily reset begins with you.” At the bottom, there is a button “GET STARTED,” below it a link “Already have an account? Log in.”2. RegistrationAfter pressing “Get Started,” a survey begins with 5 steps (Step 1 of 5). The first question: “What is your main goal?” — options: Better Sleep, Less Stress, More Energy (selected), Better Focus. The “NEXT” button leads further through the steps.3. Reminder SettingsAfter the survey, the user sets the time for two reminders — morning (08:00) and evening (20:00), with an explanation that the app will remind them to take the capsules. The “SAVE” button.4. Morning ResetWelcome screen: “Good morning, Sarah ☀️,” “Day 8 of your Reset,” an illustration of capsules with a glass of water, instructions to take the morning capsules. The “I DID IT ✓” button — the user marks completion.5. Late Check-in / Evening ResetDark screen with the moon — “Evening Reset,” text “It’s time to relax and take care of yourself.” The “I DID IT ✓” button.6. Reminder if Evening Intake is MissedIf the user forgot to check in, a screen appears “Hey, Sarah! ” with a tired emoji icon, text “You haven’t marked your evening intake yet” and two buttons: “Yes, do it now” (main) and “Later” (secondary).7. Main DashboardAfter onboarding or logging in, the user lands on the main screen: “Hi, Sarah! ,” a motivational phrase, a block “Current Streak — 8 days ” and a circular indicator “Progress — 80%.” At the bottom, the navigation: Home, Progress, Calendar, Me.8. ProgressTab “My Progress”: current streak (8 days), “Days completed 8/10” with a progress bar, weekly tracker (Mon–Sun with marks completed/missed), overall “Overall progress — 80%.”9. CalendarTab “Calendar”: monthly view (June 2025), days marked by color — completed (green), today (blue), missed (red). The user can click on a specific day.10. Day DetailsWhen selecting a day (June 8, 2025), a detailed screen opens: status of morning (08:15 ✓ Completed) and evening (20:05 ✓ Completed) intakes, plus a “Daily note” field with the user’s personal note.11. Your ResultsScreen “Your Results” — comparison of metrics “Before” and “After” (Energy, Sleep, Stress) in the form of progress bars that visually show improvement. The “SEE MY JOURNEY” button.12. MotivationScreen “Daily Motivation” with a background photo and an inspiring quote: “Small daily actions create big changes.”13. AchievementsTab “Achievements”: list of earned rewards (First Step, 7 Days Streak, 10 Days Streak) and the next goal (“Next achievement — 30 Days Streak,” progress 8/30).14. ProfileTab “Profile”: avatar and user name (Sarah), list of settings — Personal Information, Reminders, Notifications, Subscription, Help and Support, and the “Log Out” button.

We are looking for an iOS developer to create an app similar to Mindly, to work closely with our backend developer. Currently, there is no separate design, as I want to create an MVP as quickly and cost-effectively as possible. I suggest using a minimalist interface with standard UI components, without individual design. The logic and layout of elements in Mindly can be used as a basis: a central node, child nodes around it, simple navigation between nodes. There is no need to copy the design exactly; it is enough to implement a similar UX. After launching the MVP and validating the idea, a separate UI/UX can be created to improve the visual part. Screenshots from Mindly are attached. MVP technical task for an app similar to Mindly General idea The app allows users to create mind maps in the form of a tree. The user creates a central topic, adds subtopics to it, and navigates between them. Only one level of the tree is displayed on the screen at a time: the active node in the center and its immediate child nodes around it. ⸻ Main functionality of the MVP 1. Creating a map After opening the app, the user can create a new map. Only one field is needed: Map title. After creation, a root node is automatically created. ⸻ 2. Main screen On the main screen, the following are displayed: the central node; child nodes around it; a “+” button to create a new node; a “Back” button; map menu. ⸻ 3. Creating nodes When the “+” button is pressed, a small window opens. Fields: Title. Note (optional). After saving, the node is added as a child to the current one. ⸻ 4. Viewing a node When a child node is pressed, it becomes the central element. Its child nodes are displayed around it. ⸻ 5. Going back The “Back” button returns to the previous node through the history of transitions. ⸻ 6. Editing a node By long pressing or through the menu, an editor opens. You can change: the title; the note. ⸻ 7. Deleting a node Through the menu, the user can delete a node. All its child elements are deleted along with the node. Show confirmation before deletion. ⸻ 8. Saving All changes are automatically saved after each action. A separate “Save” button is not needed. ⸻ Data structure MindMap interface MindMap { id: string; title: string; } Node interface Node { id: string; mapId: string; parentId: string | null; title: string; note: string; } ⸻ Logic of operation Create a map. Create a root node. Display the root node in the center. Get all child nodes. Arrange them in a circle around the center. When a node is pressed, make it the new center. Load its child nodes. Repeat the cycle. ⸻ MVP screens 1. List of maps a list of all maps; a “Create map” button. 2. Map screen the central node; child nodes; an add button; a back button. 3. Creating / editing a node Fields: Title. Note. Buttons: Save. Delete (only for existing nodes). ⸻ What is NOT included in the MVP Cloud synchronization. Collaborative editing. Node colors. Icons. Drag & Drop. Search. Export. Import. Undo / Redo. Attachments. Tags. Reminders. Statuses. Zooming. Map templates. ⸻ Main goal of the MVP To allow the user to: create a map; create an unlimited number of nested nodes; navigate between nodes; edit them; delete them; automatically save all changes. This is enough to validate the core idea of the product without implementing secondary features.

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.