Дополнительный функционал для базы данных

Development of a Telegram Mini App (store) with CRM and Nova Poshta integration It is necessary to develop a Telegram Mini App (store inside Telegram).Main functionality A catalog with approximately 20 products is needed. For each product: photo; name; description; price; model selection; color selection; quantity. Order processing The client must have the ability to: view the catalog; add products to the cart; change the quantity; place an order; enter: name; phone; city; Nova Poshta branch number; payment method; order comment. CRM All orders need to be automatically transmitted to the CRM via API. It is preferable that the integration is universal and in the future, the CRM can be changed without a complete redesign of the project.Nova Poshta Integration with the Nova Poshta API is needed or data transfer to the CRM if the creation of the shipping document will be done by the CRM itself.Administrator A simple administrator mode is needed: adding and editing products; changing prices; changing stock levels; adding new colors or models. Important The project must work as a Telegram Mini App (not a regular bot with buttons). The code, database, and all access after the completion of work must belong to me. The architecture must allow for additional features to be connected in the future without a complete redesign. Please inform: Estimated cost. Completion time. What technology stack you plan to use. Do you have experience in developing Telegram Mini Apps and integrating with CRM and Nova Poshta API.

Location: Remote Type: Full-time / Part-time Company: Dante Labs(dantelabs.us) -About the Role We're building a platform similar to TradingView, enhanced with advanced AI-driven capabilities. Our goal is to empower users with intelligent market predictions, sophisticated analytical tools, and next-level charting functionalities to support smarter trading decisions. The platform is being developed with a strong emphasis on clean architecture, scalability, and seamless performance across frontend and backend systems. We're looking for talented engineers who are excited about building high-performance, data-intensive applications at the intersection of finance, AI, and Web3. What You'll Do - Design and build scalable backend services and APIs - Develop responsive, high-performance frontend interfaces - Integrate AI-driven analytics and prediction models - Ensure reliability, security, and low-latency performance - Collaborate with product, design, and AI teams to ship features Who You Are - Strong experience in backend development (Node.js, Python, Go, or Rust) - Solid frontend skills (React, Next.js, TypeScript) - Understanding of financial data, trading platforms, or market analytics (a plus) - Experience with blockchain or Web3 (a plus) - Passion for clean, testable, and scalable code - Comfortable working in a fully remote, fast-paced environment What We Offer - Competitive compensation (USD or crypto) - 100% remote – work from anywhere - Flexible hours - Opportunity to shape a high-impact product from the ground up - Work with a global, talented, and supportive team How to Apply To apply for this role, please complete the following steps: -Complete the home task Visit the following GitHub repository and follow the instructions in the README file(blockchain task only): https://github.com/dantelabs-team-8/fullstackblockchain -Record a Loom video Once you've completed the task, record a short Loom video walking through your solution and results. -Send your submission *Email the following to hr[at]dantelabs[dot]us: *Your CV *A link to your Loom video *(Optional) Any additional notes or context about your solution -Next steps Our tech team will review your submission. If it meets our expectations, we'll invite you for a technical interview and move forward in the hiring process.

A Telegram bot needs to be developed in Stand Pulse for the client's test. The test has 5-7 questions with 5-7 answer options. Based on the client's answers, the bot will calculate scores and provide a result (6 options).

An experienced Laravel developer is required for the integration of a payment system into an existing project. About the project Backend: Laravel Frontend: React Project: cloud file storage platform (similar to Dropbox) What needs to be implemented Integration of credit card payments via the payment system API. Creation of a payment. Redirecting the user to the payment page. Handling successful and unsuccessful payments. Processing callback/webhook. Checking the payment status. Correctly changing the order status after successful payment. Logging API requests and responses. Functioning in both test and production environments. Requirements Excellent knowledge of Laravel. Experience in integrating payment systems (bank APIs, etc.). Experience working with REST APIs. Will be an advantage Experience in integrating bank payment gateways. Ability to show similar projects. What we will provide Complete technical documentation of the payment system. Access to the test environment. When responding, please indicate: 1. Which payment systems you have already integrated. 2. Cost of work. 3. Completion time. 4. Examples of similar projects (if available).

TECHNICAL TASK Development of a Digital Signage system for a network of advertising screens 1. General description of the systemThe system is designed for remote management of media content (video, images) on a network of televisions running Android TV. Architecture:Backend / Control Panel (Admin Panel): PHP (Laravel / Yii2 or pure PHP) + MySQL.Frontend (Player on TV): HTML5 / JavaScript (Single Page Application), which runs on TV in full-screen mode via the Fully Kiosk Browser app.2. Functional requirements: Control Panel (Admin Panel on PHP)2.1. Screen (Television) ManagementAbility to add/remove screens in the system.Each screen is assigned: Name (geo-point), unique ID (device_token), and status (Online/Offline).Monitoring (Ping): Displaying the TV status in real-time. If the TV has not sent requests for more than 5 minutes, color its status red (Offline). 2.2. Content Management (Media Library)Uploading files (video, images) to the server.Deleting files (with automatic deletion of the physical file from the server).Ability to view (and modify) on which screens each individual media file is broadcasted.Setting the playback order of files. 2.3. Server API (for communication with TV)Implement REST API (JSON):POST /api/ping — receives its ID from the TV, records the last activity time (for Online status), and returns the current playlist version.GET /api/file/device_token — returns the current JSON array with links to media files, their order, and display time settings.3. Functional requirements: Client Player (HTML5/JS on TV)The player is a web page that is opened on the TV. The main task of the client is autonomy.3.1. Caching and Synchronization (Offline Operation)Upon startup, the player requests the playlist via the API.Local Storage: All files from the playlist (video/images) must be loaded into the internal memory of the browser (using Cache API or IndexedDB). Streaming (playing directly from the internet) is prohibited.Synchronization: If new content is added on the server, the player loads it in the background without interrupting the current display. After loading is complete, it adds it to the broadcast. If content is deleted on the server, the player must remove it from the local TV cache to avoid filling the device's memory.Offline Mode: In the complete absence of the internet, the player endlessly loops the last successfully loaded playlist. 3.2. Playback and RotationCyclic playback of content and according to the order set in the admin panel.For images, the display duration in seconds must be set (default 10 sec).Transitions between videos must be smooth, without black screens and noticeable page reloads. 3.3. Logging and Error Control (Failure Protection)Handling Corrupted Files: If a video file is corrupted and cannot be played, the player must skip it and turn on the next one in order, rather than hanging on a black screen.Show Logs (Analytics): The player must record in local memory the fact of each successful playback of a video. When the internet is available, this data is sent in batches to the server (POST /api/logs), so that statistics can be viewed in the admin panel: "Video A on TV #3 was shown 450 times in a day and 2365 times in total".4. Optimization Requirements for Android TVThe player interface must not contain any control elements (cursors, scroll bars, buttons). Only clean content on the full screen.JS code must be optimized for memory (timely clearing unused DOM elements and object URLs), as budget televisions have strict limitations on RAM and may crash the tab due to memory leaks after 12-24 hours of continuous operation.