Skip to content

Latest commit

 

History

History
119 lines (75 loc) · 7.67 KB

README.md

File metadata and controls

119 lines (75 loc) · 7.67 KB

GeoSeek

GeoSeek Beta on Apple TestFlight

GeoSeek allows us to connect with our family and friends while engaging in our community in a fun and gamified way! Incentivize community and a more active lifestyle Create location-based sense of magic within our local community Create a sense of the Thrill of the Hunt

Contributors

Jerry Haaser Dan Morse Brandi Bailey

Swift Version License Carthage compatible CocoaPods Compatible
Platform PRs Welcome Maintainability

Project Overview

GeoSeek aims to be the name for creating engaging experiences through technology while promoting community engagement and physical activity.

GeoSeek allows you to place and find user-created and curated hidden gems within your local community.

Search the map for gems close to you. Travel to the location and see the amazing features of that location!

Know of someplace great? Maybe a breathtaking view at sunset or a part of your town that’s a little less travelled but holds great historical significance! Whatever and wherever the case, create your hidden gem and share it with others!

GeoSeek Beta on Apple TestFlight

You can find our progress on our Trello Board

Features

  • Register & Login
  • View a world map with Gems and Zoom in to see individual Gems
  • Click on a Gem to see it's detail, and mark a Gem found!
  • Create a Gem at one of your favorite locations, for others to find!

MapBox

GeoSeek uses the MapBox iOS SDK and API

Requirements

  • iOS 13.0
  • Xcode 11
  • Cocoa Pods

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct. Please follow it in all your interactions with the project.

Issue/Bug Request

## Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct. Please follow it in all your interactions with the project.

Issue/Bug Request

If you are having an issue with the existing project code, please submit a bug report under the following guidelines:

  • Check first to see if your issue has already been reported.
  • Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
  • Create a live example of the problem.
  • Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.

Feature Requests

We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.

Pull Requests

If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.

Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.

Pull Request Guidelines

  • Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  • Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
  • Ensure that your code conforms to our existing code conventions and test coverage.
  • Include the relevant issue number, if applicable.
  • You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.

Attribution

These contribution guidelines have been adapted from this good-Contributing.md-template.

Documentation

Our Backend was built by our Backend team and can be found here: https://github.com/Lambda-School-Labs/geoseek-be