A company built on strong first principle thinking. ๐ Questioning everything is a habit that is very uncommon and finding the "WHY" behind every single thing, as hectic as it sounds, brings out some of the best results. A habit everyone should include in their daily life. ๐
Notes from my meeting with Kailash Nadh (CTO, Zerodha) last week:
1/15 They don't track users. Ever. No funnels or metrics. Their policy is to build great products from scratch, so there's never a need to track and โfixโ things later.
We previewed Scripting last night at the @rive_app NYC meetup with @duolingo!
Scripting lets you build entire experiences directly in the Rive Editor โ and ship them anywhere with the Rive Runtime: websites, apps, games, products, vehicles, and more.
@aaguueeroo You donโt need Firebase as your backend to send PNs. Just create a project, add google-services.json, initialize Firebase, and get the FCM token. Store it in your backend and use it to send notifications via FCMโs API. Itโs free, simple, and reliable, no need for alternatives IMO
@verry_codes@schultek_dev@ChrisMarxDev Have you used freeze for immutable classes? Is yes, did you find any difference or found it easier to implement thank freezed? Would definitely check it out if it makes it a lot more easier...
Finally!
This is exactly how @stacked_apps manages state.
It's simple, works well, and clearly separates UI and state.
Good on you for taking "a stand" on an architecture @FlutterDev
Veeeeeeery happy we're not only recommending BLoC anymore ๐
@kunalb11 Less negligence cases! Saving people from complications due to medical negligence because of over worked staff+doctors and reducing deduction errors/delays makes it a win. Google says there are about 5.2M such cases every year in india alone (reported). Much more depth in it IMO
A cool new update for everyone โย
You can now see the LIVE order count on @zomato for the day, right after you place your order. I just placed an order at around 11am, and the count was already over 250,000.
Have fun!
Excited to unveil India's first crowd-supported weather infrastructure, https://t.co/qE9kkfoisG. A proprietary network of 650+ on-ground weather stations, it is the largest private infrastructure of its kind in our country.
These weather stations, developed by Zomato, provide localised, real-time information on key weather parameters such as temperature, humidity, wind speed, rainfall etc. Currently available across 45 large cities, we are expanding this in other Indian cities very soon.
This rich data holds significant potential in unlocking weather use cases for enterprises and research institutes. Having already collaborated with CAS - IIT Delhi, we expect more institutions and companies to benefit from this and contribute towards the greater good of our economy.
At Zomato, it was crucial for us to have access to precise and real-time weather information to make the right business decisions to serve our customers better. Hence, we took it upon ourselves to develop a solution capable of empowering us on this front.
We are now opening up free access to this (through an API) to all institutions and companies in the country. Wait. What? Free? Really? Yes, we believe that this data is too valuable to keep to ourselves or to monetise; therefore, as a Zomato Giveback, we are opening up access to this data to everyone for public good. Multiple companies and public institutions should use real-time weather data, to boost the productivity of our economy.
Also, a lot of Zomato employees have hosted weather stations at their homes. As we look forward to further expanding this infrastructure, we welcome volunteers who want to provide us space on their premises to install these weather stations and contribute to nation building.
Isn't airchat just an audio tweet feature for X ? What happens when X simply releases an update with audio first tweets (observing retention/growth @ Airchat) will the users really stick with airchat or will it become another case study like clubhouse @getairchat@naval#AirChat
@DaneMackier@rive_app Very interesting. I'm curious though, i see you are building an entire view in rive. How will you be able to fit this across different sizes? Also, suppose i like a spacer widget between the bottom button and content above, will this approach take away that control over view?
@DaneMackier@rive_app Insane, correct me if i am wrong basically @rive_app will be used to design the i/o of the assets and can be worked out by the designer himself by just giving variables accessible to dev, devs don't have to write cumbersome animation code and the experience comes out amazing?
I've been on a mission to find a more fun way to build mobile app UI's.
Today I built an onboarding Flow using my expriment.
Here's my results:
Experience
I design the UI in @rive_app and then load it into my app.
The feeling of completing a design you like, then it showing up EXACTLY AS IS, with 0 additional UI code is an amazing feeling.
The UI above appears and animates exactly as it shows up here. See video comment.
The code
To load up this UI I have a wrapper around the rive widgets.
This widget allows me to specify the artboard to load and listen for tap events (like on the bottom right button).
This is all the code to load an artboard, and listen for onTap events.
This is the same for all three of the other views.
Dislikes
1. Adding tap events
The process for adding tap events into a UI is a bit cumbersome in rive, it's a 3 step process which could be a lot easier.
(It wasn't built for that so it's understandable)
2. Not type safe (yet)
As you can see in the code I have to reference the artboard for an expression view using the name as a string.
The same thing internally in the ExpressionView when it comes to handling events.
I read and pass the event name back as a string, which I don't like.
Improvements
My goal is to build a type safe framework where a rive file generates something like below:
As you can see, there is no artboard name, and I wouldn't have to read the eventName to know which even fired.
It would fire a specific callback based on the event name given in the designer.
Next steps
I'm building an app that I'm publishing to the store using this, so next up is a bottom sheet for google and apple sign in.
See you in the next update.