lambertf917 / lambertf917/cafe-ordering-system-using-react-js
[$100] Paid task re-implementation of Google Authentication
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The goals for this task is testing ease of use for running the project locally.
The task needs to be completed for enatega multivendor customer app module for mobile specifically. Its a reimplementation of Google Authentication feature. Below I am going to go through its details for the issues in the existing implementation.
Currently the app does not support Expo Go method and can run in development build only for which builds needs to be created which causes issues in overall development experience.
Your task is to implement Google Authentication that it can run in both Development and Expo Go method without creating any builds.
To successfully pass the criteria for this test here are the requirements.
1- Running npm install and npm run commands should only be needed
2- The project should run by scanning QR Code for all below devices and scenarios
a) Android Physical Device
b) iOS Physical Device
c) Android Emulator
d) iOS Emulator
e) Google Sign In and other functionalities of the application should work
f) Overall very major changes should not take place in the code and should be a simple and clean solution
g) Expo Login should not be a step
i) You are open to upgrade Expo SDK
Competition Deadline: 23rd June 2024 Sunday 23:59 GM +5
Submissions:
You need to meet the following criteria for submissions
1- Submission made before deadline
2- Starred the Repo
3- Forked the Repo
4- Made the Repo Private
5- Added developer@ninjascode.com as collaborator
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the customer app's existing Google Authentication implementation and its Expo configuration; the issue names no files or tests. Compare the current development-build flow with the requested Expo Go flow across the four listed device scenarios, and consider the work done only when npm install and npm run plus QR scanning support authentication without Expo Login or new builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100