The problem AFSC: Automatic Form Securing and Collection solves

Our aim is to restructure the banking system by making the process of form dispensation and deposition fast and hassle-free. That implies no more standing in long queues or going to various counters to get the form verified and submitted. We tend to go from clueless to queue-less banking systems. This device will make things easy for all age groups by blending the right technology and appropriate innovation. The era of Covid-19 demands digitization of conventional methods used in the banking sector. This machine helps us to make the process fully contactless and easy to attempt. Branch banking is expensive and requires an ample amount of capital and human resource investment, therefore our machine securing very limited space can be installed anywhere. These forms can be examined and approved in the main branch at once.
Working of the machine - QR-code will be embedded on the machine display and an individual can operate the machine by just scanning the QR code, after scanning it will be redirected to our website where he/she can find numerous forms present. On clicking the right form, printing will be started. The form can be submitted on the same using upload feature or by just scanning it in the machine.

Challenges we ran into

Designing the website cross-platform is a tricky problem. A bug that we encountered was that the window.print() was a command used in scripts extensively and had a very unique limitation, which was that since the android platform browsers do not have native support for printing yet. So, due to that, we were not able to get the same results on an android phone. However, we found a way to bypass that by using the .onclick() method and after some brainstorming, we got the idea for treating that bug and it will be taken care of. One more interesting problem was in index.js where we used a snapshot of our uploading task to showcase on the progress bar which caused a little bit of problem but later using the task.on() method helped to solve this problem. The Firebase SDK has default security authentication rules which are strict and it makes it difficult for anyone to connect the files to the mainframe. Since we were unaware of the security rules of storage made hosting the website properly a very difficult task. However, upon research and a lot of reading, we found about this problem and changed the rules according to us giving us flexibility with how the storage system will interact. On successful hosting of the website, we tested the performance of the website on “LIGHTHOUSE” and it was merely 69 but clever image optimization and rewriting of scripts, omitting comment code blocks and clearing many more bugs, we were able to get a score of 96.