Software Engineer, @importahq | Founder, @xelabytestudios, @merjup_game

Joined April 2022
Xela | You Should Play MerjUp Today! retweeted
Are you playing it safe or chasing the bigger merge? Try MerjUp: merjup.com #MerjUp #ArcadeGame
1
1
13
Xela | You Should Play MerjUp Today! retweeted
As a founder, your biggest risk flight is not knowing how to find solutions to problems you face while building for scale. Before @importapay_ng there was @Importahq, finding solutions for Importa brought ImportaPay to live, crossing $1m volume mark already, with client across Botswana, Guinea, Cameroon, Ghana and Nigeria. Are you a fintech, payment provider, IMTO, in need of a regulated payment solution, at near instant settlement, great rate, fees 90% lower than what traditional providers, with multi currency access. Reach out let’s talk today.
4
13
1
51
1,586
Xela | You Should Play MerjUp Today! retweeted
That feeling when two cans finally merge. 🔥 Toss. Merge. Rank Up! merjup.com #MerjUp
2
2
13
Xela | You Should Play MerjUp Today! retweeted
I finally put together a summary of my experience at @solanaturbine , and it is an interesting read!  Whether you're planning to join the cohort, already in it, or not, I'm sure there's something you can learn from my experience. Give it a read, and feel free to ask me any questions and I got my certificate, yay! Link: dev.to/ladipo_samuel_7cfaa82…
3
12
121
1,433
codex has been so bad lately considering the claude max plan atp 🫩
20
Xela | You Should Play MerjUp Today! retweeted
Still in the news. After getting our MSB, we have started leveraging it exposure and potential to improve our business corridors, business model, and product type. At ImportaPay. Regulatory coverage means a lot to us, and therefore this is a great start to what else we will be capable of doing in the future 💜
We’re building cross-border payment infrastructure for businesses operating across markets. Our MSB registration in Canada is another step forward. More to come. #ImportaPay #Fintech
4
11
294
prediction: within a year mobile game teams will treat the daily reward lock as a scheduled job with its own tests, because a next goal set that opens at the wrong hour quietly trains players to stop checking the app at all #MobileGames #Retention
1
13
Xela | You Should Play MerjUp Today! retweeted
From a Turbin3 student to a graduate! What a journey! Lots of learning and assignments, Mehn😂 Really gonna miss the calls, seeing @umacanadas face, and collaborating with some amazing people. Built something I'm really proud of with my teammate @Haileyesus_be too! Big thanks to @solanaturbine and our peak instructors, @qubitn8 , @umacanadas , @Princeadxisrael , @shrinathx , @me256ow and @Moses7054 . And a special thanks to @toby_solutions , who encouraged me to start this journey in the first place. I'll be sharing more about my experience and what we built, and things I learned over the next few days. Looking forward to building and contributing more to the @solana and wider Web3 ecosystem.
Solana just got 51 builders stronger From the prereqs to getting your capstones out on demo day, we saw how much work you put in over the last two months. So give yourselves a proper pat on the back 💚 We're proud of every one of you, and we’ll be cheering for your wins as you keep growing in this ecosystem. And you’re part of the Turbin3 Tribe now. That doesn’t come with an end date.
6
10
3
158
3,047
til: a paid goal dated by sync time instead of by the games it pays will drift out of its daily lock, so derive the goal date from the games themselves and players stop seeing a reward window that opens twice or never #MobileApps #Retention
5
honestly, your mobile app's retry copy is where trust gets decided, because a player who taps a paywall and sees a spinner with no reason will assume the app stole the purchase, so name the failed step and give them a retry #Subscriptions #MobileUX
7
jsyk: reporting a finished rewarded ad to Meta as an impression is the difference between an analytics number you can defend and one that quietly inflates your mobile app's ad revenue while the payout stays flat #AppMonetization #MobileApps
1
10
jsyk: when your android app can't open the google play payment sheet, a silent failure reads to the player as a broken purchase, so surface the reason and a retry path instead of letting the tap do nothing #MobileApps #Subscriptions
11
til: on android, marking the foreground service as started too late leaves the app open to a fatal crash when the notification fires, so declare the type in the manifest and call startForeground before the first await #AndroidDev #AppPerformance
1
23
prediction: within a year the mobile release note teams stop writing as prose will be a machine diff of what actually changed, because users who see the exact crash patch and screen named tap update faster than any polished changelog #AppStore #MobileApps
1
22
ngl: an app store screenshot that fakes a feature the mobile app doesn't have yet is a churn machine, because the install that follows is a trust loan you pay back with a one-star review within the first session #AppStore #MobileUX
3
57
ngl: your app's notification inbox can betray you when a tapped push opens the feed instead of the exact thread, because that mismatch is what trains users to stop trusting mobile notifications entirely #MobileUX #Retention
7
jsyk: an android app that fires every push at high priority trains the os to treat all of them as noise, so reserve the urgent flag for the overtake alert and your retention notification actually lands when it matters #AndroidDev #Retention
1
13
jsyk: the first-week goals card is really an onboarding surface, because a new player who can see all seven days mapped out has a reason to return tomorrow instead of closing the mobile app after one session #Retention #Onboarding
12
ngl your app's onboarding checklist is the quiet retention lever nobody audits, because a new user who can see exactly what to do next stops hunting for the first win, and every unfinished item is a reason to come back tomorrow #MobileUX #Onboarding
7
til: your mobile app's offline queue can quietly replay the same payment intent twice when the sync retries after a flaky connection, so stamp each queued action with an idempotency key and the duplicate charge never happens #MobileApps #AppDevelopment
1
4
22