Progress Reports

Project Progress Reports:

 * Stage I Report: Researched existing project to see what is wanted/needed, experimenting with flutter. 

* Stage II Report: Flutter will not work, switching to split development. Basic backend is made but further work is needed for both frontend and backend 

* Stage III Report: Frontend nearing completion, backend nearing completion and the tying together both of them so frontend contacts the backend, server up and running on digital ocean, webclient in production

* Stage IV Report: iOS version in active production. Android version in production pending Play Store review

 

 

Meeting Minutes: 

(Week 2) | 9/3/25

Initial meeting at Reiman Gardens :

  • Keep server time-costs in mind.
    Android / IOS need seperate developments. Each must be native.
    We'll have access to previous code to reference
    Playstore and Appstore credentials will be provided (appstore version will be an 'unlisted' publication)
  • Need to add voice channel, general client communications, and credential channels to discord
  • IOS Background / Lock screen functionalities are a no-go. Don't waste time on these.
    Both Android and IOS need widget functionality.
  • 15th-day of month thing is borked in current version. (facility rather than butterfly o' day)
  • Map only shows the 5 closest, so no need for a scrolling list of facilities below map.
  • Previous month lookusp is unimportant. Don't waste time on this.
  • Initial update has been 2am, with a redundant update window a few hours later.
  • Web interface currently for database scrolls back to the top after an info update. Would be nice to update in place.
  • Android pictures should auto-size without issue. IOS is fiddly with this, requires pre-editing for photos. 
    This should already be done.


     Server : Digial Ocean
    Test software : Test Flight

General responsibility track
-------------------------------                
IOS team : Seth, Nayan
Android team : Jason, Jacob
DB overlap : Seth, Jacob
UI overlap : Jason, Nayan

 

(Week 4) | 9/16/25

  • Met with client in person. Worked through access issues. Discussed current work plans.

(Week 5) | 9/23/25

  • Discussion of current project status
  • Discussion of planned database rebuild
  • Discussion of timing for code replacements, client desire for minimal downtime noted
  • Discussion of back-end login discovered in old code

(Week 6) | 9/30/25

  • Brief in-person meeting. Light discussion, then client departed again so that we could finish prep for presentation.

.(Week 7) | 10/7/25

  • Back end progress: New Mongo DB running.  
  • Nayan: iOS calendar working.
  • Concern about getting the full array of butterflies for calendar app use.
  • Continuation of back-end interfacing idea. Idea about using scientific butterfly name as DB key rather than a butterfly_id field.
  • Further discussion about DB, JSON, month function possibly, date parameters, (year/month specified format) URL Params for back-end?
  • storing the month-to-date stuff. Call current day - look for previous days - call for those as necessary - call for "today" specifically.
  • Aesthetic discussion w/Nathan for next week. Butterfly info desired? Handled merge requests

(Week 8) | 10/14/25

  • Butterfly images - image params for client info (height, width, resolutions, etc.) There's one horizontal image / one vertical image. image name (m/f/n - male female ; h/v horizontal, vertical; e/b exhibit, butterfly). Male/females should have seperate day showings as they can look differently. Day reset should be consistent with locality - don't want someone in China having two butterflies in a day - should key against the user day. App should send the date to the server, so it can return the 'day's butterfly. Server is assigning the day's butterfly.
  • Test flight / apk checking - probably around week 10-11. (be sure that November 15th is available to check). Need to get on this ASAP so that we have daily test data to check over. Calender view showing photographer? Scrollability important for calendar butterfly info.
  • Modify map size on Android app to get all 5 cards showing. Butterfly of the day graphic - logo. Be sure corners are rounded. Important client desire.
  • Getting it onto the App/Play store prior is important.
  • Review android app photo requirements. Check BoTD email for play store notes, requirements, ToS rules.
  • Android Fold? Need to account for that!
  • Database handoff w/provisional backup.

(Week 9) 10/21/25

  • About page should be editable via the web interface (one per platform) - and then may be pulled by the app as needed.
  • Map - no jumping w/IoS.
  • Map pins being able to pull exhibit page/web page would be great, whether or not they're top 5.
  • Database modifications - Male vert/horz, Female vert/horz - add, removes
  • If facility has no image, leave blank
  • Pre-generating butterflies - pulling some ahead may make the time zone thing less an issue.
  • Be able to sort database via # of photos, to identify entries without images.  male / female versions important to be used as individual BoTDs.
  • Sorting by male, female, null, etc.
  • Consider accessibility options for theme color options

(Week 10) 10/28/25

  • Met with client. General discussion of status and direction.

(Week 11) 11/4/25

  • Joined by Anita today (client adjacent)
  • Web development starting next week
  • Editing of butterfly page discussed
  • BotD must have image assigned.
  • Droplet question - in terms of new backend
  • Front-end projecting basic feature completeness end of this week
  • Folding, background, lock screen
  • Download option for iOS / wallpaper - little round the corners, but would still kinda work
  • Icon - scrap it on the top nav bar - rework it completely for launch icon - toooo many colors. Make it simpler. Possibly even just use previous graphic for that.
  • More facilities coming. Sorting by 'not having things' would be great. Easier to isolate butterflies w/out pic - able to search butterflies.
  • Unified color scheme discussed
  • Accessibility things - description stuff - research / apply - make sure we're going to fit uni guidelines
  • ** IMPORTANT ** Maybe a database field?  Colorblind friendly?
  • Map reset to USER page - Need to do this one.  ** IMPORTANT **
  • Android - maybe lighten the cream color?

(Week 12) 11/11/25

  • Met with client. General discussion of status and direction.

(Week 13) 11/18/25

  • FrontEnd:
    Ensure widget sizes work, maybe by cropping images instead of stretching,
    Finish up development
    Have the map screen show facility pictures when they are tapped
    Get ready to deploy to stores.
  • Backend:
    Set up authentication for dev requests,
    Set up certificate for server
    Create way for images to be uploaded
    Have the web client able to edit existing data (edited)Wednesday, 

    Discussed accessibility needs to be in compliance w/University policy

Thanksgiving Break Here

  • No Meeting This Week due to break

(Week 14) 12/2/25

  • Met with client. General discussion of status and direction.

(Week 15) 12/9/25

  • Butterfly of the Day Instructions - video link
  • Privacy Policy and Visit Website may stay as written
  • Route to Butterfly of the Day privacy policy, rather than University - tweak prior to use
  • Discussed accessibility feature addition
  • Discussed scheduling of pushing apps to the play/iStores
  • Approved of 'Fold' phone version images

(Week 16) 12/17/25

  • android update issues - assured client of post-semester update commitment to finish up final polish
  • Discussion of how facilities are influenced to join the group
  • server droplet rename
  • Timing for playstore
  • iOS push schedule
  • Handover discussions
  • Back-end updates
  • Schedule for final presentation