Release

This is the homepage for the Release project

Current Projects

UP Innovation AwardsUP Innovation AwardsDeadline 14th Aug 2023 Tasks * [ ] MVP Figma - Tuesday 8th August * [ ] 20 Validations - Wednesday 9th August * [ ] Scripts and presentations one by one until 11th August * [ ] Video Recording - 12th and 13th of August * [ ] Final details and submitting application - 14th August Pasos (Documentacion) * [x] Pitch elevador sobre tu proyecto * [x] Problemática a resolver * [x] Cliente Ideal * [x] Tamaño del mercado * [x] Solución viable, factible y deseable * [x] Demo de la solución * [x] Repo

Release/Developer/stackRelease's Tech StackI want to have a familiar Tech Stack to build Release's Mobile app. This are the priorities for the technologies we'll choose: Shipping* features as *quickly as possible** * Having type-safety for confident refactoring * Use familiar tech, so new devs get up to speed quickly Multiplatform** development For this reason, these are some of the major decisions regarding the Tech Stack. 1. We structure our code in a monorepo, where we can develop each app separately and share code between them. W
scaling-frontent-applicationsScaling Frontend ApplicationsPrinciples 1. Tear down the barriers Migrate to a Monorepo! People can re-use packages. Keep developers excited! 2. Make it easy to delete code Codebases get large, and that's fine. However, we should encourage having as little code as possible, therefore making it easy to get rid of once it's not needed anymore. An example is colocation of styles in React components using something like Tailwind CSS. This will make developers more confident on deleting a whole component without worrying i