Developing a farm management system Stage 1

Hi, I'm looking for a skilled DB/web developer to help develop a farm management system. I have an airtable database which is providing some limitations, particularly in the UI. The chosen developer needs to be highly skilled in UI design, particularly in mobile formats. The UI will need to be concise and easy to use as the end user will have limited time to interact with the system. The system will look after management 'blocks' of a farm. The four management functions on the blocks will be 'spray applications', 'irrigations with fertiliser or treatments', 'harvest' and 'jobs'. Spray application and harvest are the two most important to start. Spray application (Spray Diary) needs to access a number of tables including 'Chem Inventory', 'blocks', application 'method'. 'Chem Inventory' holds records of chemicals purchased that are ready to apply. Chem Inventory accesses table 'Chemicals' Fields: Chemical Name, Date Purchased, Expiry Date/Batch number, Withholding period, application rate, rate units. In the UI, upon entering the Chemical Name, if the Name is already in the 'Chemicals' table then proceed to populate the fields: Withholding period, application rate and rate units. The user should be able to override the imported values. The user should also be prompted to enter the purchase date and expiry date/batch number. 'Blocks' is a very important table in the system, it is essentially a management unit in a farm. Blocks will be built upon in the future but the most important function is to interlink activities on the farm to the harvest which will proceed right through to the delivery to market. Fields: Block Name, Farm number, size, variety, planting date. Application 'Method' table keeps records on equipment such as spray tanks and spreaders. Fields: Name, purchase date, capacity, calibration date. 'Spray Diary' table holds records of treatments on a number of blocks. Fields: Date, Application method (Method>Name), Blocks (Blocks>name, can select a number of blocks), Area treated (blocks>size aggregated but can be altered), Date (todays date but can be altered), Tractor Speed, Wind Speed, Wind Direction, Operator, Chemical Name (Chem Inventory>Name. Can add more than one chem name. possibly up to 6 different chemicals but usually only 2-3. The user should be able to tap a button to continue to add new chemicals). For every chemical added, the record populates the corresponding data for the selected chemical: application rate, rate units, Withholding period. These fields should be able to be overridden. For Spray Diary, it is worthwhile considering the use of a second intermediary table to hold the chemicals used. possibly calling it 'tank mix'. Upon viewing records in Spray Diary, we should be able to edit and duplicate records. Harvest table is used to record a unit of harvest that will be needed later in stage 2 of the project. Fields: Lot (autogenerated), block (blocks>Name), bins. The user cannot change the Lot. That's all I can think of at this moment, please feel free to ask questions as we go.