Lines up across all five SOLID principles after the fact. That wasn't the goal it just falls out when you keep the base closed and let config do the variant work.
Write-up: https://t.co/jLzTVmMK1w
Same bottom sheet. Seven times. Almost.
That's the trap, the photo-picker in my inDrive clone's driver-onboarding flow. Collapsed seven near-identical sheets into one base component + thin presets that vary on three knobs: actions, content, examples (layout-as-data).
Ride-hailing apps have been one of my personal projects I've always been eager to build. I Just completed the passenger onboarding and ride hailing flow for my @inDrive clone. No backend yet just dummy data
up next is the drivers and courier onboarding and flow, follow by backend integration using Django.
If you're building in the mobility or logistics space and looking for a technical co-founder or a mobile engineer to join your team I'm open to that conversation. DM me or connect
@tomilola_ng Guess I wasn't the only one thinking about this.. I'm currently building an InDrive clone to have a feel of what it needs to be done, I'm done with passenger flow though. Once I conclude the passenger and driver flow I'll start building the backend.
@youngdaraey@tomilola_ng Any reasons why I shouldn't?, I'll have to refetch bank API response if the cache expires. it doesn't cost the DB nothing, I could cache the db queries as well I don't need to make external API calls if users need to add or update bank details
The lesson I keep relearning building this app: the features that feel "small" to users are almost always the ones with the most moving parts.
What's a feature you've shipped that turned out to be deceptively complex?
You type "@" in a group chat. A list pops up. You tap a name. Done.
Looks trivial. It isn't.
Just shipped @mentions on my WhatsApp web clone. What's actually happening:
Keystroke-level trigger detection (is "@" a mention or part of an email?)
DTO Fields:
content: raw text, mention inline so legacy clients still read it
member_id: stable ref (group membership row, or __ALL__ for broadcast)
display_name: snapshot, fallback when local resolution misses
offset / length: positional span; renderer slices and replaces
@goodmanncapital@TuoyoS26091@paystack It doesn't work out of the box you just need to add your logic in your code to make it work as expected.
Yes sadly it belongs to the company I worked for
@goodmanncapital@TuoyoS26091@paystack Plans, it all depends on how he implements the logic, like I said it's a recommendation I'm not saying his approach is bad or he has to follow what I said. it worked for me and at the of the day it's getting the job done that matters
@goodmanncapital@TuoyoS26091@paystack Relax you're not getting the point, Maybe I didn't explain It quite well due my Twitter's limit, yes paystack doesn't support trials I was recommending the subscription and plan endpoint to handle the trials due to recurring charge benefits after the trials when paying for other