/flutter-doctor-consultation-app

Doctor consultation app designed using flutter.

Primary LanguageDart

doctor-consultation-app

Maintenance ForTheBadge built-with-love ForTheBadge made-with-flutter ForTheBadge ios-supported ForTheBadge ios-android

Hypertension Awareness & Management application built with Flutter

❤️ Found this project useful?

If you found this project useful, then please consider giving it a ⭐️ on Github and sharing it with your friends via social media.

Download the APK

In Github, Go to flutter-doctor-consultation-app releases, choose the version (latest is recommanded) and download the .apk file.

Install the APK

On your Android phone:

  1. Go to Settings > security > install unknown apps.
  2. Go to files and enable Allow from this source. Don't forget to disable it when you have finished
  3. Exit Settings and go to files.
  4. Go to Downloads, select the .apk and click install.
  5. The app is now installed on your phone.

Getting Started

This project is a starting point for a Flutter application.

To clone this project, open your terminal or cmd

cd folder/to/clone-into/

git clone https://github.com/madeeldev/flutter-doctor-consultation-app.git

Then locate the project on your system and open with android studio or Vscode or intellij IDE.

To Run:

C:\path\to\project> flutter pub get

then run:

C:\path\to\project> flutter run

Build release version

run: flutter build <OS PLATFORM> e.g flutter build ios

Resources

A few resources to get you started if this is your first Flutter project:

For help getting started with Flutter, view our online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.

Prerequisites

What things you need to run the app

* Android Studio/Vscode/Intellij IDE
* Flutter SDK
* Android SDK
* Windows/MacBook

How to contribute

  • Fork the repository and clone it locally. Connect your local to the original “upstream” repository by adding it as a remote. Pull in changes from “upstream” often so that you stay up to date so that when you submit your pull request, merge conflicts will be less likely. (See more detailed instructions here.)
  • Create a branch for your edits.
  • Reference any relevant issues or supporting documentation in your PR (for example, “Closes #37.”)
  • Include screenshots of the before and after if your changes include differences in HTML/CSS. Drag and drop the images into the body of your pull request.
  • Test your changes! Run your changes against any existing tests if they exist and create new ones when needed. Whether tests exist or not, make sure your changes don’t break the existing project.
  • Contribute in the style of the project to the best of your abilities. This may mean using indents, semi-colons or comments differently than you would in your own repository, but makes it easier for the maintainer to merge, others to understand and maintain in the future.

Built With

Author 😊

Adeel Safdar