We've raised a $40m Series B to build the one app for all things DeFi & Web3. And to prove the future of crypto is self-custody - not giant exchanges.
We'll use the funding for:
1. Product development
2. Expanding into Latin America
3. Hiring
Read on to learn more 🧵
@danielolivalx > Há quem, na direção do PS, prefira ir para eleições.
Acho que podemos dizer que a pré-campanha já arrancou:
https://t.co/11byDJuota
@manuelmaly One container/feature view that renders the underlying view for each status. Adding some transitions tomorrow. In the end it’s the most flexible approach.
I was trying to move into a state modelled by an enumeration and use `SwitchStore` from the Composable Architecture but I have to keep the intermediary states until the very end...
What if we derive a status from the optional states and we use that instead? 🚀
@manuelmaly I considered that option but one or two screens are going to be reused in other flows of the app, e.g. Settings to change your email address, and that would cause a problem at that point.
@manuelmaly Yeah I was using a `NavigationView` for it but ended up scrapping it, it works well for the simple flow where you are just pushing and popping one or two screens but state restoration was a nightmare with it so I ended up abandoning it.
@manuelmaly Optional states for each screen, I'm collecting email and other data as part of onboarding, when you go back I need to restore to the previous state, one by one... Didn't find a way with an enumeration to be able to access all the previous states.