Skip to content
It's an app for the UC bearcat bands
Branch: master
Clone or download
Latest commit b957d57 Jun 17, 2019


It's an app for the UC Bearcat Bands


The way things are currently swinging, we need a database-backed web API. The current play is with this one:

  • Django - A "batteries-included" python web-framework
    • To make coding a REST API easier, Djano-Rest-Framework is hella nice.
    • P.S., the way the Django project is currently structured is not something I'm strongly attached to and I'm willing to move the "app" folder (bands) outside of the project folder (ucbearcatbandsproject) if we determine that'd be easier to work with.

For frontends, we are doing two UIs:

  • A traditional web application. We currently have a demo written in Blazor, a framework for making Single-Page Applications (SPAs) using C#/.NET. We have other options:
    • Django? - Django Templates would allow for us to create a web-frontend which tightly integrates with Django, but not Django-Rest-Framework. As a result, we wouldn't be able to use the REST API if we roll with this for the site, thus we'd essentially need to maintain two APIs. However, it does integrate cleanly otherwise.
    • Instead of using Django Templates, we can also use a "traditional" javascript UI framework for building the site. IF we use one of these, we'd be able to use the REST API we are maintaining for the mobile app, plus they have solid developer communities and are quite powerful. However, it's another thing we'd need to learn and figure out.
      • Angular - A Typescript Framework for web applications; Mature and tested. Supported by Google Open Source
      • React - "A JS library for building UIs" - Supported by Facebook Open Source
      • Vue.JS - "Approachable, versatile, performant " - Newcomer of the trio, but it does have the most momentum. Fully community supported, w/o the grace of a core dev team of an existing corporation.
  • An iOS only mobile app
    • Details about our configuration / setup are below.

Set up Information

The Django Backend

  1. Make sure you have python 3.7 installed.
  2. Install pipenv using pip to facilitate package downloads.
  3. In the cloned directory for the backend (the one with, run pipenv install to grab all the dependencies.
  4. Run pipenv shell to activate the virtual environment you just made with the above line.
  5. If there isn't a db.sqlite3 in the directory, run the following command now:
    python migrate
  6. Noodle away

The Blazor Frontend Demo

  1. Install Visual Studio 2019 (version >= 16.1) and make sure to include the ASP.NET and web development workload during installation.
  2. Install NET.Core 3.0 Preview 5
  3. Install this extension to enable Blazor support.
  4. Execute the following command in a terminal window (powershell, cmd, etc):
    dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.0.0-preview5-19227-01
  5. Back in VS now, enable usage of .NET Core SDK previews (Tools > Options > Environment > Preview Features > Use previews ...)
  6. Pop open that solution and get cracking!

The "Actual" Fronted


iOS App Setup

Since the iOS app is really just going to be a frontend wrapper for our web API, I'll go ahead and suggest you set up a backend server. The app won't really do much if it can't ping that.

After you've done that, do the following to work on the iOS app:

  1. Have a Mac (or run macOS)
  2. Download the Xcode IDE.
  3. Install CocoaPods, used as a package manager in the same vein as pip for Python.
  4. Inside the "MobileApp" directory, you'll find a file named Podfile; this specifies our dependencies. Run pod install in the terminal to install them.
  5. Open the MobileApp.xcworkspace file in Xcode, and everything should be ready to go. Note that you don't use MobileApp.xcodeproj, it's not tied into the CocoaPods dependencies.

Ben has some lingering concerns about code signing (requires an iCloud account and he's set it up to use his), but this should more or less work. If you run into issues consult Ben.

You can’t perform that action at this time.