At Silly Labs we develop interesting projects, that's a given. If you would like to know more about what's available, what we're working on, and what's in the pipeline, feel free to select a project above and enjoy what's here, coming, or being mulled.

It should be noted these are our currently active projects. If you're looking for one of our previous joints, please search for the project using your favorite search engine. When a project has run its course we try to either open it up to the greater community, or, if that's not possible, they are retired.

If phones are not desktops, laptops, or tablets, why do they follow the same desktop-like design metaphors? Phones are hand-held touch-centric devices which we interact with through fluid gestures. Should we need multiple screens with icons, and folders to hold even more icons? We don't think so.

Motus is different than other launchers. Built on our design principles, Motus aims to offer a more graceful approach using four simple directions to simplify a users launcher experience. Think Motus might be something you're interested in?

At SillyLabs we develop projects based on five guiding principles we call SECSI. While some projects are less beholden to some aspects, a command-line utility needs less customization than a full-fledged desktop application or mobile app, and hardware projects have decidedly less customization than software, these guiding principles are used to develop all SillyLabs projects. If you feel we’ve neglected a principle in some respect, please let us know through the contact area.

Projects developed by SillyLabs must be secure and transparent. Any bugs and/or faults must be promptly fixed with updates pushed as expeditiously as possible. Furthermore, updates must document these aspects rather than gloss over or otherwise them. While hardware projects may have multiple revisions released, they should build upon a secure foundation. A safe and informed user is a happy user.

Nothing is more appalling than an ugly implementation which requires greater resources than necessary. If anything, software should get faster as hardware grows resource wise, and hardware should be designed to be as performant as possible. Any feature which does not have equal or greater performance on current hardware as it had on the directly preceding generation must be re-evaluated implementation wise. Non-bloated software is paramount, while hardware must be designed with performance in mind.

In so far as the software warrants, users should have the ability to customize software as they see fit. Simply because User A enjoys using something one way does not mean all users should be required to do the same. Likewise, not all users have the same abilities, accept this and develop solutions which attempt to facilitate accessibility as permitted. Finally, hardware, wherever possible, should be designed with the ability for users to customize without restriction. Want to make a new enclosure? Sleeve the wiring? Go for it! One users back is another users forward, one users disco lights are another users seizure device, embrace it.

A wise person once said, “Everything should be made as simple as possible, but not simpler.” When it comes to SillyLabs projects we strive to do exactly that. Understandably we start with a simple foundation and grow as required, but we must always be aware of the overly complex and strongly limit the impulse to add unnecessary complexity. KISS is SECSI.

Simply put, projects should be interesting for both users and creators. If either party is not engaged and interested in the project that’s being used and created, it’s time evaluate other options. Now this may be as simple as putting a feature hold on the project to evaluate its future, to even open-sourcing it to allow the community writ large the ability to take over the project. Without interest in a project they tend to wither, and things that wither tend to die. Keep things interesting, both for users and as creators.