Budget: 15000 UAH Deadline: 12 days
Let’s look at the full tz and other details and assess properly your project. I look forward to the answer, good day.
Budget: 15000 UAH Deadline: 12 days
Let’s look at the full tz and other details and assess properly your project. I look forward to the answer, good day.
Budget: 12345 UAH Deadline: 30 days
I can take. Experience is great. I work quickly, my colleagues on the insurance. FOP, we sign a contract, we take guaranteed obligations. The cost and deadlines are agreed. More details about us on pancodix.com
Budget: 1000 UAH Deadline: 1 day
Hi you I understand the backend has already been implemented, you need to download the data from it and the documentation or at least a swager or something like where you can get acquainted with the methods on the basis of which the application will work.
Applications for delivery from restaurants have already been implemented, you can see in my profile in the portfolio.
I can implement the application on Flutter at the same time on both IOS and Android platforms.
After obtaining the necessary data and discussion, we will be able to compile technical tasks and divide it into tasks.
If you don’t have a backend, we can develop it according to a technical task.
Budget: 68800 UAH Deadline: 120 days
We will fulfill your project and we will follow you after the release.
Mobiwolf.com has been in existence since 2010. We specialize in the development of comprehensive mobile solutions under the platform Android, iOS. The majority of our customers are foreign customers from the United States and Europe.
Our meetings, portfolio and other details I suggest to discuss through a personal chat.
Budget: 500 UAH Deadline: 1 day
Victoria, a good night.
Approach (as for the courier and the office): from 80-120 hours
Server Part: from 40 to 80 hours
Parts responsible for printing: from 20 hours
It lasts 140 to 220 hours. Depending on the final set of functionality.
1 . It should be carefully recorded the entire process of passing the asset and all operations with it.
The 2nd Design and approval of architecture
3 . Design the design and forms of the reporting, insert.
and 4. Adjust the time assessment, make a development plan with the risk consideration.
and 5. The development
6 . Testing and deployment of the system.
7 . Reporting and submission of the project.
Budget: 67999 UAH Deadline: 20 days
Hello to you!
Our team has been developing mobile apps for more than 7 years and we are ready to implement your project. However, in order to provide a cost-and-development spot, you need to get acquainted with the full TZ and the design of your app.
Budget: 30000 UAH Deadline: 30 days
Victoria, hello to you
I don’t really understand one moment, you have one application using both the courier and the buyers?
Usually, two separate applications are used in such business solutions.
They communicate with themselves on the net. (one for the customer who uses the product, the other for the courier, etc.)
Reply to the question)
Budget: 1234 UAH Deadline: 1 day
I will be able to develop for you an app for Android, native (Kotlin/Java) with further support.
The price, the deadlines, and so on, we will discuss more. to turn.
Shortly about yourself - commercial development experience on Android 8 years. Extended CV and examples of works - on additional request.
Budget: 68800 UAH Deadline: 30 days
I have 7 years of Android development experience. Interested in your project, but you need more details to assess the deadlines and value. If you have a detailed TZ, then I would like to get to know.
Budget: 1234 UAH Deadline: 30 days
Hello, I'm ready to make this application on React Native (Android + iOS)
I have 5+ years experience in developing mobile applications
My portfolio is: Freelancehunt
My GitLab: https://gitlab.com/users/m.polazhynets/projects
My technical skills:
JavaScript and Typecript
React Native and React
Redux
Firebase✅✅✅✅
Development of a Power App, support for me as a beginner. Canvas App, assistance in developing the Screen Help in developing the data structure for the App Programming functions Assistance in creating Date-verse Tables
We are looking for an experienced Shopify developer to create a full-fledged online store from scratch with mandatory integration with Amazon. What needs to be done: Integration with Amazon as the foundation of the project: synchronization of products, inventory, and orders between Shopify and the seller account on Amazon. The store setup is built with this integration in mind from the very beginning. Store setup: theme customization, catalog structure, product cards, cart, checkout — everything is aligned with the logic of integration with Amazon. Technical optimization for AI visibility (GEO): structured data, llms.txt file, content optimization for AI assistant responses (ChatGPT, Perplexity, AI Overviews, etc.), proper semantic markup of pages. Basic SEO setup: meta tags, sitemap, loading speed, mobile responsiveness. Connecting payment systems. Installing necessary applications (reviews, email marketing, analytics, etc.). Testing the store before launch.
Need help rethinking and building a clean relational schema for an internal operational system on Airtable. The current database is already in use by the team, but it has grown organically: the structure is partially flat, some tables/views are actively used, while others are hardly used, and documents currently rather "pull" information into Airtable, although ideally Airtable should become the source of truth and generate the necessary operational artifacts. What is needed is not just help with forms or automations, but structural work: analyzing the current logic, designing a relational schema, creating a clean new database/instance, documentation, and recommendations for migrating to the new schema. And potentially even implementation. System context: There are two main directions: Feedback system A system for collecting and processing signals from external advisors, focus groups, internal teams, and stakeholders. It should support: signal log; advisor tracking; feedback intake; synthesis dashboard; status/gates/recommendations; close-the-loop logic. Product catalog The product catalog currently has about 400 entries, approximately 100 of which are active/live. It is necessary to better structure products, statuses, relationships, data sources, lifecycle/gate logic, and reporting. Current state: Airtable already exists and is used by the team. The current data accuracy is about 80%. The schema is mostly flat, not relational. Only the first few tables/tabs are actively used: Some validation gates, tasks/decisions, and dashboard views are currently hardly used. There is no PII. Any work with the live base must be done with maximum caution: no changes in production without agreement. The ideal approach is to analyze the structure and build a new clean base separately in Sandbox. What needs to be done: Phase 1 — Audit & architecture recommendation Look at the current structure of Airtable. Determine which tables/fields/views are actually needed, which are duplicated, which can be merged or removed. Propose a relational data model. Describe the main entities, relationships, primary keys, linked records, lookup/rollup logic. Propose a clean schema for the Project + Product catalog. Determine which dashboards/interfaces are needed for different users. Prepare a short architecture memo or schema map. Phase 2 — Build clean Airtable base Create a new clean Airtable base/instance. Set up tables, fields, linked records, views, basic interfaces. Set up basic dashboard/reporting logic. Prepare a migration map: how to transfer data from the old structure to the new one. Document the structure so that the team can maintain it after handover. If necessary, propose an automation strategy, but without excessive complexity. Expected deliverables: Airtable schema map. A new clean Airtable base. Tables + relationships + key fields. Views/interfaces for main users. Migration recommendation. Short documentation for the team. Governance recommendations: who enters data, who approves changes, which fields are mandatory, how to avoid duplication. Optionally: 1 short handoff call / Loom walkthrough. Important security/access rules: No PII. No dangerous tokens or personal integrations. AI/MCP/ChatGPT/Claude cannot be connected to live Airtable. If access to the existing base is needed, it must be read-only or through export/screenshots/structural description. Any records/changes are made only in the new test/clean base, not in live production. Who I am looking for: The ideal candidate has experience in: Airtable base architecture; relational schema design; Airtable interfaces, views, forms, automations; migration/cleanup of messy Airtable bases; product operations / CRM / workflow systems; documentation and handoff. In your response, please indicate: Examples of Airtable bases or systems you have built. Whether you have experience transforming a flat Airtable structure into a relational schema. How you would approach audit → schema design → build. An estimated number of hours for Phase 1. Your hourly rate or fixed-price proposal for the first phase. Whether you are willing to work under an NDA. Work format: It is preferable to start as soon as possible. Initially, a small paid discovery/audit can be done, after which we can move to the full build.
Need to update the offer agreement in the footer to a new one, the company has changed its regulations Task will take 20 minutes