Devin W.C. Ryan

Tracking Ideas & Back-end Considerations

I’ve been doing more thinking on this and would like to actually get something off the ground this winter.  Perhaps by scheduling an hour or two every week dedicated to working on it.  First off, I have some things I need to explore as I’ve been reconsidering implementation.

The 3 areas I plan to focus on tracking to start are:

  • Books (read / want to read)
  • Quilts (for the wife)
  • Puzzles
  • R/C Plane Projects

I have already laid out the foundation for the first two, so going to focus on Puzzles first.  The key things to track would be:

  • Brand
  • Title
  • Size / Dimensions
  • Pieces
  • Picture (of the completed puzzle)
  • Date Completed (Time would be nice, but not sure we will have that data, at least for past puzzles)

For R/C Planes it is going to work like an inventory/ building project tracker.  For this I’ll want to track the following:

  • Manufacturer
  • Type: Kit, ARF, RTF
  • Name
  • Wingspan
  • Engine
  • Acquisition date
  • Year of purchase & completion date

I will want the ability to tie images with entries as well, except for in the case of books perhaps.

I am considering trying Firebase for the back-end instead of my original plan of using AWS to learn something new and provide a comparison since I’ve already done an iOS app,  Healthy Environments, for work using AWS.  As far as graphics go the app itself will be minimalist as this would not be my strong suit, but maybe I’ll find some inner creativity!

And a better name for the app 🙂

Leave a Comment

Your email address will not be published. Required fields are marked *