Development of subscription functionality (Part 2)

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.

Task Description: We are looking for a developer to create a simple web-based parking space management system without monthly paid subscriptions, turnkey.What is available: A detailed parking layout in DWG (AutoCAD) format. In total, about 500 parking spaces.Main task: It is necessary to transfer this layout to a web interface so that each parking space becomes clickable and dynamically changes color (for example, Green — Free, Red — Occupied). This is an electronic register for long-term rentals (manual data entry by the manager is planned; automation with sensors, barriers, or cameras is not needed).Role distribution and access: Manager: Works from a computer in the office. Has access to the "admin panel," where they can change the status of each parking space (free/occupied) and enter a description (for example, the name of the renting company). Security: Located on the premises, connects from mobile devices (phone, tablet, or laptop) via mobile internet. Security has view-only access (Read-only). They click on a space and see information: Space number, Status, Company name. They do not have the ability to change anything.Implementation requirements: Turnkey work: from adapting the layout for the web to deploying the system and database. The map interface must be responsive for easy scaling and finger clicks on smartphone screens. Propose the optimal way to host the system: either deploying on our office PC (external access setup will be needed for the security's mobile internet) or using free cloud limits.Please, in your response, suggest your version of the tech stack and architecture (where it is better to host the database so that security has access from 4G), and also indicate the estimated cost and timeline for the project. Important note regarding budget and functionality: The project is being done exclusively for internal use and basic convenience. We DO NOT need complex design solutions, CRM systems, integrations with payment gateways, SMS notifications, and the like. We need a maximally simple, concise, and functional interface without excess code. Therefore, please assess the project adequately — offers with overpricing will not be considered. Thank you.

Experienced OpenCart developer needed for project acceptance and further support I am looking for an experienced OpenCart programmer (not a studio) who can professionally accept the online store from the current developer and will further handle its support, development, and SEO optimization. About the project Online store on OpenCart. The project is approximately 99% ready and verified according to the technical specifications. A technical audit needs to be conducted before the final handover of the site. After the handover, long-term cooperation for project development is planned. Main tasks Conduct an audit of the code and project structure. Check the quality of the implemented functionality. Check the installed modules, their compatibility, and correct operation. Assess the security and stability of the site. Check the performance and suggest recommendations for improvement. Check the implemented SEO part and propose a further optimization plan. Ensure that the project is fully ready for independent support without dependence on the previous developer. Check the correctness of the transfer of all accesses: source code; database; FTP; hosting; domain; email; administrative panel; installed modules and their licenses. If necessary, participate in communication with the current developer during the project handover. Provide a list of recommendations and comments before the final acceptance. Further cooperation After the site acceptance, regular work on the project is planned: development of new functionality; SEO optimization; performance improvement; integration with external services; technical support. Candidate requirements A specialist is needed who: has significant experience specifically with OpenCart; has a good understanding of OpenCart architecture and popular modules; has experience in auditing and supporting existing projects; can reasonably assess the quality of completed work; takes agreements seriously and adheres to agreed deadlines; is interested in long-term cooperation. In your response, please indicate experience working with OpenCart; examples of implemented online stores; whether you have conducted technical acceptance or audits of other projects; estimated cost: technical audit; participation in project acceptance; hourly or project support after the handover. Preference will be given to specialists with many years of experience working with OpenCart, who take their work seriously, adhere to agreed deadlines, and are ready to become a technical partner of the project for the long term.