Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/pkini2002/ar-ecommerce-app
An AR - Ecommerce App built using Java for the backend and Firebase database
https://github.com/pkini2002/ar-ecommerce-app
android-app android-studio-java augmented-reality firebase firebase-authentication-android sceneform-sdk xml
Last synced: 6 days ago
JSON representation
An AR - Ecommerce App built using Java for the backend and Firebase database
- Host: GitHub
- URL: https://github.com/pkini2002/ar-ecommerce-app
- Owner: pkini2002
- Created: 2023-04-07T15:40:24.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-05-08T10:03:41.000Z (6 months ago)
- Last Synced: 2024-05-08T11:26:40.653Z (6 months ago)
- Topics: android-app, android-studio-java, augmented-reality, firebase, firebase-authentication-android, sceneform-sdk, xml
- Language: Java
- Homepage:
- Size: 3.75 MB
- Stars: 5
- Watchers: 1
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# AR-Ecommerce-App
## 📌 Problem Statement
The problem statement for this AR e-commerce app project is to provide an immersive
and interactive shopping experience to the users. Traditional e-commerce platforms offer
limited product visualization, which makes it difficult for customers to make an informed
purchase decision. With the implementation of Augmented Reality (AR), customers can
view 3D models of the products in real-time and make informed decisions about their
purchases.
The AR e-commerce app aims to solve the following problems:
- Limited product visualization: Traditional e-commerce platforms offer limited product visualization, which can result in a higher number of returns and unsatisfied customers.
- Inconvenient size and fit: Online shopping makes it difficult for customers to determine the perfect size and fit for their desired product. This leads to a higher number of returns and unsatisfied customers
- Lack of interactivity: Traditional e-commerce platforms lack interactivity, whichcan lead to a monotonous shopping experience.
## 💻 TechStack Used
- `Java`
- `XML Design (Frontend)`
- `Firebase database (Realtimedb, Cloud Storage and Authentication db)`
- `Augmented reality SDK's`
## 📸 Screenshots
## 🚧 To-do's
- [ ] User's Session Management fixes (Includes View Profile,View Cart and Logout)
- [ ] AR Product Visualization for each and every item present in a category
- [ ] Payment Integration
- [ ] Delete items from Cart
- [ ] Twilio Messaging API Integration on checkout
- [ ] AI Chatbot integration
- [ ] Admin Login and Admin Specific Page View (Upload data)
## Steps to clone the project
```bash
git clone https://github.com/pkini2002/AR-Ecommerce-App.git
```
```bash
cd AR-Ecommerce-App
```
**Do necessary changes if any and add your code to the staging area**
```bash
git add .
```
**Commit the changes with a text message.**
```bash
git commit -m "Message"
```
**Create a branch**
```bash
git branch dev-branchname
```
**Push the code to your branch**
```bash
git push origin dev-branchname
```
## Steps to be followed if you have already cloned the project
**Add the changes if you have done and commit it**
```bash
git add .
git commit -m "Message"
```
**Switch to main branch if not in main**
```bash
git checkout -m main
```
**Pull the changes**
```bash
git pull origin main
```
Now You can start working and once there is an update/a feature which needs to be pushed follow the same steps mentioned above
*Note: Sometimes the changes gets reflected once you close and open the project in Android studio. So make sure to do so*
> - Use [semantic commit messages](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716) to keep the commit history clean.
Semantic commits
```
[optional scope]:
[optional body]
[optional footer(s)]
```
- feat – a new feature is introduced with the changes
- fix – a bug fix has occurred
- chore – changes that do not relate to a fix or feature and don't modify src or test files (for example updating dependencies)
- refactor – refactored code that neither fixes a bug nor adds a feature
- docs – updates to documentation such as a the README or other markdown files
- style – changes that do not affect the meaning of the code, likely related to code formatting such as white-space, missing semi-colons, and so on.
- test – including new or correcting previous tests
- perf – performance improvements
- ci – continuous integration related
- build – changes that affect the build system or external dependencies
- revert – reverts a previous commit