Goals for Metrics on the Wix Constructor

I am a professional 3D designer, creating highly detailed renders of monuments and memorial complexes (vertical format 9:16). My clients are workshop and studio owners who need a convenient digital catalog of my models to show to their retail customers. What I need: To select the optimal platform and create a lightweight, fast web app (catalog) that will look perfect on smartphones and open correctly on computers. Key requirements for the catalog: Design: Maximum minimalism. Dark theme (black background), large vertical image (proportions 9:16), with only the name/article of the model below it. No long descriptions. Database management: I need a very simple system for adding new models (ideally through familiar Google Sheets or a very user-friendly internal database). I should just be able to upload an image and enter the article number without breaking the layout. Client integration (Most important): The catalog should be easily integrated into the websites of my workshop clients (some use WordPress, others have custom-built sites). An elegant embedding method needs to be thought out: via Iframe (so the catalog works directly within their page) or through proper button-link setup. What I have already tried: I tested Glide and Adalo. In Adalo, I achieved the desired visual (9:16 on a black background), but managing the internal database and dealing with Google Drive links turned out to be too inconvenient for regular use. Plus, I have doubts about correctly embedding Iframe into other websites so that it doesn't misalign on wide monitors. What I expect from you in the response: On which platform (Adalo, Glide, Bubble, Webflow, Glide + Airtable, or something else) do you propose to implement this and why? How will the issue of storing heavy images (renders) be resolved? How do you propose to technically embed this catalog on the external websites of my clients? I am looking for a specialist who can handle this technical pain point turnkey, so I can focus on 3D modeling.

The website is already launched and operational. The main task is to understand the current project structure, check the quality of implementation, fix identified technical issues, and assist with further changes.Main Stack Next.js 15 React 19 TypeScript Tailwind CSS Zod Redux Toolkit The project may also use: Prisma JWT authorization Stripe Mailgun Google APIs Vercel or Netlify FunctionsMain Tasks conduct an audit of the existing project; evaluate the structure and quality of the code; fix bugs and enhance current functionality; improve server-side rendering and page load speed; check the correctness of the website display on mobile devices; work with forms, the administrative part, and external integrations; make technical SEO changes; maintain and gradually improve the existing website.What is Important to Us good experience with Next.js, React, and TypeScript; ability to understand someone else's code; understanding of SSR and the features of Next.js App Router; attention to performance and quality of implementation; ability to explain identified problems and propose clear solutions; independence and careful work with the existing website. At the first stage, it is necessary to familiarize yourself with the project, conduct a technical audit, and propose a list of priority changes. After that, ongoing work on the further development of the website is possible.

We are looking for an experienced Embedded developer to create energy-efficient firmware for a wearable device (form factor: chest strap) for monitoring psychophysiological state. The circuit design is complete, and development will be based on a development kit with subsequent transfer to a custom board.Stack and hardware base:MCU: Nordic Semiconductor nRF52840 or nRF5340.Development environment: nRF Connect SDK / Zephyr RTOS (strictly C/C++).Peripherals:Optical pulse sensor (PPG) — operates via I2C.6-axis inertial sensor (IMU accelerometer + gyroscope) — operates via SPI.Haptic motor driver (LRA 1030) — controlled via PWM.External SPI Flash memory for cyclic logging.Work scope by stagesStage 1: Bring-up, peripheral drivers, and BLE telemetryGoal: Bring the hardware to life, set up stable data collection, and transmit it to a smartphone/PC.Configure I2C and SPI buses using DMA (Direct Memory Access) to offload the processor.Write/integrate drivers for PPG and IMU (configure polling frequency, sensor FIFO buffers).Deploy a custom BLE profile (GATT service) for real-time transmission of raw data from sensors.Basic initialization of PWM for controlling the haptic LRA motor (launch test vibration patterns).Stage 2: Algorithmic layer (DSP and multi-level feedback logic)Goal: Implement mathematical signal processing directly on the chip (Edge Computing) and device reaction logic.Implement algorithms for filtering motion artifacts: clean the PPG signal using accelerometer data (IMU).Extract R-R intervals (HRV) from the cleaned PPG signal.Implement 4-level system stability logic:Drift Level: Track gradual changes in HRV and breathing.Prediction Level: Calculate a mathematical trend for deterioration.Micro-correction Level: Generate barely noticeable haptic patterns on the LRA motor when a target data pattern is detected.Hardware Reset Level: Implement safety logic (high-intensity haptic pulse at critical metrics).Stage 3: Energy saving, logging, and fault toleranceGoal: Prepare the device for autonomous operation from a miniature battery and ensure "24/7" stability.Deep optimization of energy consumption. Put the MCU into sleep mode (System ON/OFF) between measurement cycles. The processor should wake up only on interrupts from sensor FIFO buffers or a timer.Write a fault-tolerant file system in external SPI Flash (e.g., LittleFS) for autonomous cyclic log saving.Configure a hardware watchdog timer to prevent firmware hangs.Requirements for the performer:Experience in commercial development for Nordic chips (nRF52/nRF53) of at least 3 years.Proficient in Zephyr RTOS and debugging tools (Segger Embedded Studio / VS Code, J-Link).Understanding of digital signal filtering principles (DSP) and low-power design.Having your own debugging kit (nRF52840-DK or similar) for starting work is welcome.Work format:Milestone payments with results documented on GitHub. Please indicate your hourly rate or approximate cost and timeline estimates for each of the three stages.

Need a Wix specialist for website layout based on Figma design. There is a ready website design in Figma. It needs to be implemented in Wix with high quality, closely following the layout. Requirements: transfer the design from Figma to Wix; adapt all pages; set up desktop and mobile versions; ensure correct display on different devices. Preference will be given to freelancers with experience working with Wix. Please send your portfolio with completed projects.

General information It is necessary to develop a simple minimalist web system, the main purpose of which is to maintain a client database, create appointments for visits, and automate the process of confirming visits via SMS, sending one-time links through the API from the service itself. The project is being developed in stages. In the first stage, it is necessary to implement only the basic functionality (MVP) so that the system can be used in real work. After launch and testing, it will gradually be expanded with new modules.Main functionality of the first stage User authorization; Client database; Creating and editing appointments; List of appointments (or a simple calendar); Switching between points of sale; Integration with the SMS operator via API; Sending SMS with any text or link for visit confirmation; Confirmation or cancellation of the visit by the client via a one-time link; Displaying the confirmation status directly next to the client's appointment. At the initial stage, instead of a full calendar, the use of a simple list of appointments by days is allowed. Each day should contain a chronological list of bookings indicating the time, client's name, service, employee, and confirmation status. Later, this list can be replaced with a full calendar without changing the system structure. The system must have the ability to switch between points of sale. Each point of sale has its own list of appointments (or calendar), but they all use a common client database.