Simple web app - React + azure functions
- or -
Post a project like this£25/hr(approx. $31/hr)
- Posted:
- Proposals: 35
- Remote
- #4144193
- Expired
Expert WordPress / CMS Developer| UI/UX Creation | Graphic Designs | Logo & Branding
Albany
Full Stack Web Developer | HTML | CSS | JavaScript | NodeJS | PostgreSQL | Mongo DB| React Native | React | NextJS | AdobeXD | Social Media Manager | Content Strategy | Content Creation
Karachi
Wordpress|Webflow|Shopify|Wix|CRM|PHP|Android|iOS|Bespoke|App|Zoho|Laravel|SEO|PPC|Social|React|Node|Flutter|React Native|Magento|PWA|Plugin|Chrome Extention
Mohali
Full-Stack Developer => React| Vue | Node | PHP| WordPress | Python | Django|TypeScript
Kharkiv
Sr. Web Designer + Developer (PHP/ CMS/ MVC Framework /E-commerce) + Mobile APP Developer
Chandigarh
Versatile Senior Technology Consultant | 10+ Years of Expertise in Web & Mobile Development | Proficient in Salesforce,PHP, AWS, Azure, NodeJs, ReactJs,React-Native, Flutter
Chandigarh
7554007864208088597792847358014935274936153131344247741090136264792331082625410888753
Description
Experience Level: Expert
Estimated project duration: less than 1 week
I'm looking for a developer with React and Azure functions and Azure SQL experience to build a simple web app.
The react web app will employ the SurveyJS library. It will:
1. Query Azure Functions backend to request latest survey definition file location and a response (session) id.
2. Fetch survey definition via CDN and initialise presentation using SurveyJS.
3. Fire and forget minimal post updates to backend reporting survey progress.
4. At defined moments (after key questions) POST the full (interim) survey response to backend.
5. At survey end POST final survey response.
SurveyJS will handle all survey routing and presentation.
Backend (Azure functions) will:
1. Ensure credibility of all requests (cors and/or other measures).
2. Query Azure SQL database to retrieve survey definition file location, initialise a response row in database and return id to client as requested.
3. Receive and update response status (last question completed) as notified by client.
4. Receive and update survey response data (JSON) directly to database when received from client.
Additional client notes:
The survey definition file may be of a significant size due to the size of the survey and number of language translations included (tbc). Therefore an unacceptable initial load time is anticipated, and an initial fast loading welcome page may be required while resources are loaded in the background.
IP locale detection and locale/language switching on demand would be required for the welcome page. Locale/language setting would then be passed into SurveyJS for the actual delivery of the survey. It will handle all language and locale switching once the survey is running.
Additional server side notes:
A number of the survey questions will need to load their response options dynamically via REST API call. SurveyJS handles this itself on the client side. However the server-side endpoint will need to be implemented. This should be very simple as the SQL to fetch required data is already wrapped in stored procs on the DB. You will just need to validate the request and pass parameters supplied to the stored proc then return the results in the format required.
All development will need to sit in our Git repo and be fully and automatically deployable to Azure.
The react web app will employ the SurveyJS library. It will:
1. Query Azure Functions backend to request latest survey definition file location and a response (session) id.
2. Fetch survey definition via CDN and initialise presentation using SurveyJS.
3. Fire and forget minimal post updates to backend reporting survey progress.
4. At defined moments (after key questions) POST the full (interim) survey response to backend.
5. At survey end POST final survey response.
SurveyJS will handle all survey routing and presentation.
Backend (Azure functions) will:
1. Ensure credibility of all requests (cors and/or other measures).
2. Query Azure SQL database to retrieve survey definition file location, initialise a response row in database and return id to client as requested.
3. Receive and update response status (last question completed) as notified by client.
4. Receive and update survey response data (JSON) directly to database when received from client.
Additional client notes:
The survey definition file may be of a significant size due to the size of the survey and number of language translations included (tbc). Therefore an unacceptable initial load time is anticipated, and an initial fast loading welcome page may be required while resources are loaded in the background.
IP locale detection and locale/language switching on demand would be required for the welcome page. Locale/language setting would then be passed into SurveyJS for the actual delivery of the survey. It will handle all language and locale switching once the survey is running.
Additional server side notes:
A number of the survey questions will need to load their response options dynamically via REST API call. SurveyJS handles this itself on the client side. However the server-side endpoint will need to be implemented. This should be very simple as the SQL to fetch required data is already wrapped in stored procs on the DB. You will just need to validate the request and pass parameters supplied to the stored proc then return the results in the format required.
All development will need to sit in our Git repo and be fully and automatically deployable to Azure.
Tim D.
99% (21)Projects Completed
33
Freelancers worked with
33
Projects awarded
25%
Last project
29 Jan 2024
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies