The Ideas
Start by writing down a list of ideas, and keep adding to the list whenever a new idea comes up. Eventually the ideas will have to be structured into MVP and features to add later.
- Photos are displayed in an infinite scroll of photos. This includes having to load more photos in the background. S-0003
- Getting away from deriving meaning for photo IDs or using categories for authorization. S-0004
- Allow photo file names to be anything, as far as the archive is concerned. Can still keep the existing names, but the archive should not care. S-0004
- Break the hierarchy (grouping -> set -> image) as being structural. Images are the core of the photo archive; different levels of grouping are secondary. It should be possibly to have photos which are not part of a set or any other grouping, and can only be discovered by searching. Note: may need to create arbitrary folders if needed. S-0005
- Keep track of the original file name, timestamp when the photo was added to the archive, and any updates.
- Be able to display all the “new” photos to a user (that is, photos recently added, not “new” in the sense of unprocessed).
- Enhance searching. Should have a basic search and an advanced search. People searching should be easier.
- All query results that are a list of individual photos provide those results in a consistent way.
- Consistent server-side pagination for all different query results.
- Allow for filters to be applied to any result set.
- Logged in users have access to the full-size images (edited or original); only administrators have access to the “raw” files.
- Cleanup of old user database, probably erase it completely and start anew with users. Too much junk.
- Investigating Google’s way of displaying photos on the phone. This is documented on the Google photo album page.
- Base the styling on the 2023 effort, at least for MVP. No need to re-invent that particular wheel right now.
- Consider having two “modes” for the photo app, one (the default) is geared towards occasional users, the other is geared towards the maintainer (me). Part of user preferences.
- Integrate the photo of the day into the photo archive. Photo of the day attributes are to be stored inside the archive and the PotD website used that (is possibly a thin wrapper around the photo archive).
- At some point, look into social media share options.
- Look into streamlining sharing photos from the photo archive to the blog.
- Get away from the fixed 3÷2 aspect ratio. Use the photo’s native aspect ratio in the rendering.
- It makes sense to have a reduced size for the photo to render on the web, to save bandwidth. Possibly the “m5” size currently used may be the new standard?
