Create a Google Extension error reporter
- Estado: Closed
- Premio: $100
- Propuestas recibidas: 3
- Ganador: miftahularifin
Resumen del concurso
Description:
By clicking on our extension, the user should have the function to report a websites url link to us.
We have a product that a Google Chrome extensions manifest v3
What we want to do now is to build a error/issue reporter that makes it easy for the customer to report when our product does not work.
The FE of the reporter needs to be built as a google chrome extention (manifest v3). Design is part of the task, expectation is a design that looks professional.
The backend needs to be written as a standard spring boot application connected to a mariadb database. We will package it for private cloud (docker/k8s) and setup routing/db once this is done but it will need to be testable from localhost based on instructions you write.
Description:
By clicking on our extension, the user should have the function to report a websites url link to BE (api endpoint on a server) containing information:
-which active tab the error is for (URL) and unique identifier for the extension sent to BE (1)
Use the attached icons for the chrome extension. The Icon visible to the user should have badges, one in the upper right that increases for each time the chrome content script is executed (i.e. mock another trigger we will add later). It should be visibly indicated that this number is a good thing.
Another icon badge in the lower right displays the number of unresolved errors the specific extension has reported (1). The badge should be visually presented in such a way that its obvous that its a bad thing
I.e. create an api enpoint on BE and an indicator in DB. So when we (manually in the db) change the indicator to resolved there is a BE api endpoint that the chrome extension can poll on regular basis to understand that the issue is resolved. Once the issue is resolved the number of unresolved issues displayed should be reduced by one. If no unresolved issues are availible the (unresolved) badge should not be shown.
Above the error reporting function we should write out in text current status:
--
Number of popups succesfully blocked: X
Number of popups reported: Y
Success rate: Z%
--
where Z = 100*(Y/X) rounded to 2 decimals.
Step by step
1A. Make a mockup.
1B. Get our approval of the mockup, so you dont need to do a lot of work for nothing.
2. Build it.
Habilidades recomendadas
Principales propuestas de este concurso
-
miftahularifin Indonesia
-
Towhidulshakil Bangladesh
-
Towhidulshakil Bangladesh
-
asirihewage Sri Lanka
-
Hshakil320 Bangladesh
Tablero de aclaración pública
Cómo comenzar con los concursos
-
Publica tu concurso Fácil y rápido
-
Consigue toneladas de propuestas De todo el mundo
-
Elige la mejor propuesta ¡Descarga fácilmente los archivos!