Defining the MVP

Real bare-bones MVP only shows a photo stream starting with the latest photos in the photo archive, whithout searching or filtering. No logging in.

Necessary for this:

• Retrieving photos newest first. This requires a create/update timestamp in the database and a data conversion of the existing data.
• Solving the performant stream and server-side paging problems.
• Ability to display an infinite stream.
• Ability to show individual photos with their information.
• Settings to specify the URL of the server.
• Defining a versioning paradigm, and developing support for that in the pipeline. Including the idea of having a build number in the repo which is automatically updated whenever a release is done. May just have an auto-increment of the last part? No clue how to do that. Maybe just accept that the build will always increment the last field of the version number?