Pondei

Frontend Engineer | React, TypeScript & Next.js | Building Fintech Dashboards, Payment Workflows & Scalable Business Web Apps

[Pondei @ebimopondei]

After announcing Paywise product thinking case study, the initial step was not about opening Figma or diving into React components. It was about Product Definition.

This phase involved clarifying what Paywise is, who it serves, the problems it addresses, and what v1 intentionally avoids. Paywise v1 is a payment operations visibility dashboard designed for small businesses, freelancers, startups, and finance/admin operators.

It helps users:

* monitor payment health
* investigate transactions
* understand available vs pending balances
* review settlements and payout activity
* see connected payment source/provider status
* know when action belongs in the provider dashboard

But Paywise v1 does not:

* process payments directly
* hold funds
* initiate payouts
* manage withdrawals
* manage bank accounts
* act as a wallet, bank, Stripe clone, Paystack clone, or accounting platform

That boundarisalready shaped frontend decisions.

For instance, I opted for “Balances” instead of “Wallet” because Paywise provides provider-synced balance visibility rather than fund storage. Similarly, I chose “Payout Activity” over “Request Payout” since Paywise tracks provider-owned payout records without initiating payouts.

While these may seem like minor naming choices, in fintech UI, language serves as architecture. An inappropriate label can suggest that the product controls money when it does not.

The goal with Paywise is not to build another dashboard template.

It is to show how product constraints become frontend architecture and implementation decisions.

That is the case study I am building.

[Pondei @ebimopondei]

@ekemini58110 What do you mean by "you copy the folder into antigravity"

Why do you have to copy the folder? Why not just open it up in antigravity or any other IDE?

[Pondei @ebimopondei]

@Akintola_steve I'll say you use JWT instead of having sessions.

JWTs are great for this usecase since they are designed to be stateless.

[Pondei @ebimopondei]

hi @grok,
Analyze my tweets, profile, and interactions: Gender: Sexuality: Mental Age: Hobbies: Personality Disorder: Crush: IQ: Qualifying Adjective to Describe Me: 5 Favorite Things 5 Things I Don't Like
And my secret crush here tag them

[Robinson Honour @honour_can_code]

hi @grok,
Analyze my tweets, profile, and interactions: Gender: Sexuality: Mental Age: Hobbies: Personality Disorder: Crush: IQ: Qualifying Adjective to Describe Me: 5 Favorite Things 5 Things I Don't Like
And my secret crush here tag them

[Pondei @ebimopondei]

One thing more job seekers should do:

Get a custom domain for your portfolio and set up a professional email like [email protected].

A lot of people put all their energy into improving their technical skills, but first impressions still matter.

The person reviewing your application will notice things like:
• Presentation
• Attention to detail
• Personal branding

Those small details can make a difference.

You can get .cv from @pxxl_space

[Pondei @ebimopondei]

@neo_officialll The first video I saw of her speaking, she was making sense.

Subsequent video from her just proved that she's just a woman after all.

[Pondei @ebimopondei]

@AdepetuTayo Little things that make the difference when it matters.

Couldn't agree more.

[Pondei @ebimopondei]

One thing more job seekers should do:

Get a custom domain for your portfolio and set up a professional email like [email protected].

A lot of people put all their energy into improving their technical skills, but first impressions still matter.

The person reviewing your application will notice things like:
• Presentation
• Attention to detail
• Personal branding

Those small details can make a difference.

You can get .cv from @pxxl_space

[Pondei @ebimopondei]

@Kolar_Dev What tooling do you use to manage your monorepo?

Npm workspace?

[Pondei @ebimopondei]

/Downloads/code

[maria @maria_rcks]

where do you store your projects

[Pondei @ebimopondei]

Gmail has 0 customer support for a big tech company.

You'll probably be unable to login to your account from a different device if you lost your phone and laptop where you are currently logged in.

It's scary TBH

[Pondei @ebimopondei]

I just reserved my Cloudflare Wallet tag: https://t.co/jamVQxGjw9.

Reserve yours now at https://t.co/PpSkPD2nwj

[Pondei @ebimopondei]

@AskMichaelTaiwo Una no date Gemini?

Me too

[Pondei @ebimopondei]

@EOEboh Congrats bro

[Pondei @ebimopondei]

@ekemini58110 Yes. I'll use pnpm

[Pondei @ebimopondei]

@MellydotTech Return 201 if you made a successful POST request since there's usually no reason to return the content that was created

[Pondei @ebimopondei]

@yehhmisi Exactly. Ever learning. Ever improving

[Pondei @ebimopondei]

Gmail has 0 customer support for a big tech company.

You'll probably be unable to login to your account from a different device if you lost your phone and laptop where you are currently logged in.

It's scary TBH

[Pondei @ebimopondei]

@akinkunmi Are you talking about cream crackers?

[Pondei @ebimopondei]

This screenshot 👇🏽is why you think we are saying the same thing. We are not really saying the same thing.

User is the primary entity. Wallet and Profile should both reference User and not wallet referencing Profile.

If you go proceed to store user_id on both, the fk on Profile is redundant.

So if you rather store fk of wallet to profile then your take is valid. However, that is not the best or common approach.

NB: However,there may be justifiable reason why you would want to implement it as you suggest e.g users can have multiple profiles which can each have its own wallet details.

What are your thoughts?