⚠️ Work in progress
An iPhone and iPad app where you can browse LEGO sets and parts and manage sets and parts lists, just like Rebrickable but with more features, and really fast thanks to an embedded SQLite database.
The database is seeded with data from Rebrickable and other sources, and maintained up to date with regular over-the-air updates.
A built-in, super easy to use 3D designer lets you explore and manipulate parts and create virtual LEGO builds.
A simple app where you can browse a list of LEGO part colors, using an embedded database seeded with data from Rebrickable.
A command line tool retrieves data from the Rebrickable API and creates a SQLite database file that then gets embedded into the app as a bundle resource.
Add parts. The list should show the picture of the part provided by rebrickable.
- update specs for the command line tool
- update specs for the app
- update the command line tool
- update the app
Features should be kept to a strict minimum, just enough to explore what works and what does not. User interface and experience should be just enough to make things usable. Ease of use and visual appeal should not be of any consideration.
Technical design and quality code should be the top priority. All code should be well documented and contracts clearly communicated. Code should be as simple as possible and focused on implementing the actual and current features and nothing more. Abstractions and indirections should be kept to a minimum. Refactoring should happen as often as needed to keep things well designed and reasonably maintainable. Performance and resource optimization is off topic.
Error handling is not important and efforts should concentrate on the success scenarios. Error handling code should only exist to :
- protect the integrity of the system or its outputs
- reveal errors when they occur instead of when they start breaking things Crashing the app is ok and should be the preferred way to handle errors.