https://github.com/ajinkyataranekar/nooble-app
https://github.com/ajinkyataranekar/nooble-app
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/ajinkyataranekar/nooble-app
- Owner: AjinkyaTaranekar
- Created: 2021-03-29T03:54:20.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2021-03-29T14:29:29.000Z (about 4 years ago)
- Last Synced: 2025-02-03T10:34:22.527Z (4 months ago)
- Language: Dart
- Size: 6.59 MB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Nooble App
It is a cross platform music player app using Spotify API, with Swipe Up Navigations, to listen to your favourite songs.
## Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
## Install APK [here](https://github.com/AjinkyaTaranekar/Nooble-App/blob/main/Nooble-App.apk?raw=true)
## Architecture
Name | Description | Language | Source code
----|------|----|----
Frontend | Mobile Application | Flutter | https://github.com/AjinkyaTaranekar/Nooble-App
## Requirements
* Any operating system (i.e. Linux, Windows, MacOS X)
* A little knowledge of Flutter and Python. Don't worry if you are new to it, you just need knack to learn.
* Any IDE with Flutter installed (i.e. VSCode, Android Studio, etc)
## Development Setup
### Frontend
- Install Flutter.
- Add Android Studio and setup android device or android emulator
- Now, run the ``` flutter doctor ```
#### To start App
- ``` git clone https://github.com/AjinkyaTaranekar/Nooble-App.git ```
- ``` cd Nooble-App ```
- ``` flutter pub get ```
- ``` flutter run --no-sound-null-safety ```
### Backend
## Contribution Guidelines
Please raise a feature request or issue before sending PR for the same.
Follow the below guidelines for proper coding practices:
- Always [create a new branch](https://confluence.atlassian.com/bitbucket/branching-a-repository-223217999.html) for your changes and make PR from it ONLY.
- Write neat code with proper comments.
- Follow PEP8 coding style.
- Write descriptive commit messages. Please [read this](https://github.com/erlang/otp/wiki/writing-good-commit-messages) for more information.
- Write detailed PR messages and include `fixes #ISSUE_NUMBER` it if closes an issue, otherwise use `concerns #ISSUE_NUMBER` to tag the related issues. Please [refer here](https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/) for more PR guidelines.
- It is recommended to have a single commit for a task.
- Use [DRY principles](https://thealphadollar.github.io/learning/2019/05/13/go-dry.html) to create maintainable code.
## Authors
* **Ajinkya Taranekar**
