Mobile app for Hotels.ng?

[timigod]

Very curious as to how you came about this (wrong) supply chain information.

[kananga]

@xolubi and other Paystack people

I apologize if I offended anyone, I didn’t mean to. Maybe I used the wrong choice of words. I also did not realise there was a PayStack army here

However, apart form my choice of words, I stand by my statement. I will not escalate this any further, but I’ll respond directly to some statements if you don’t mind.

@FatherMerry

Paystack runs on software we’ve lost sleep building over the past year. Lots of sleep, money and relationships went into this.

Of course you did. So did Nairabox, and SimplePay, and SlushPay, and CashEnvoy, and others who use the FlutterWave API.

@xolubi

So no, you cannot just “become a retailer too if you are interested in fintech”.

Yes you can. All you need to do is pay FlutterWave their access fee, and use their API. It is not a secret society.

Finally, to those who accused me of heresy, can you explain to me the relationship (maybe that relationship no longer exists) between PayStack and FlutterWave? And how it differs from the other companies as depicted in this image below from the FlutterWave website. Thanks

Click here to view it directly by yourselves if you wish.

[timigod]

@kananga

Finally, to those who accused me of heresy, can you explain to me the relationship (maybe that relationship no longer exists) between PayStack and FlutterWave? And how it differs from the other companies as depicted in this image below from the FlutterWave website. Thanks

It’s amazing, @xolubi gave you a long, pseudo-technical explanation, probably sitting in front of the source code while at it (because, spoiler alert: that’s his job), and yet you decide to:

1. Still ask that the relationship be explained.
2. Continue speaking like you know about the relationship better than the hands-on CTO and Front End Engr Lead.

But what is even more AMAZING is that:
There. Was. No. Flutterwave. PayStack. Had. Been. Working. For. Months. But. Somehow. They. Are. Retailers.

Except FlutterWave has a back-in-time API, it’s painfully clear that you’re WAY WAY off the mark.

[kananga]

@timigod

There. Was. No. Flutterwave. PayStack. Had. Been. Working. For. Months. But. Somehow. They. Are. Retailers.

There was no FlutterWave when CashEnvoy started either. So what?

There was no iPhone when I started using phones. Today I use iPhone. So what?

[timigod]

@kananga

There was no FlutterWave when CashEnvoy started either. So what?

I didn’t think you’ll need me to break it down. But, I mean, you keep saying things I didn’t think you’ll say. So joke’s clearly on me for not expecting this.

• FlutterWave didn’t exist.
• PayStack had to build a lot of the infrastructure themselves (as they’ve already said).
• FlutterWave exists. Possessing one section in their mark up with a bunch of logos and not much (read: zero) text detailing what service they actually provide these clients.
• But for some reason, somehow, through this lack of concrete statements and explanation from their end. You immediately decipher the relationship and all its modalities.

If the above flow still makes sense to you, I’m afraid. There’s little hope.

Plus

@kananga

There was no iPhone when I started using phones. Today I use iPhone. So what?

Come on man, come ON! Really? Like this analogy? Ahn ahn.

Sayonara.

[Nosaaaa]

You’re really insistent on being wrong. Shouts to you. Real bravery

[ekemini]

Please oooooo my Radarians I intended that you guys help me decide if every website/web app needs a mobile app especially if the website/web app is fully responsive on all device type… epp a brova and after that, y’all can continue the parri

[Nosaaaa]

Because not everything needs an app. Target market isn’t doing their internet-ing on a phone because they can afford a computer and thus, a hotel.

I might be wrong on the second part, but traffic from web is usually from users with higher disposable incomes. Like 6 times out of 10.

[kananga]

@timigod

I didn’t think you’ll need me to break it down. But, I mean, you keep saying things I didn’t think you’ll say. So joke’s clearly on me for not expecting this.

FlutterWave didn’t exist.
PayStack had to build a lot of the infrastructure themselves (as they’ve already said).
FlutterWave exists. Possessing one section in their mark up with a bunch of logos and not much (read: zero) text detailing what service they actually provide these clients.
But for some reason, somehow, through this lack of concrete statements and explanation from their end. You immediately decipher the relationship and all its modalities.

If the above flow still makes sense to you, I’m afraid. There’s little hope.

I’m sorry but that’s a lot of mumbo jumbo.

You implied that because PayStack was incorporated before FlutterWave, that it is somehow impossible for PayStack to be using FlutterWave tech. You implied that chronology is causality, it is not. As clearly demonstrated by the examples I gave you - CashEnvoy has been around since 2009, they use FlutterWave tech, this shows clearly that your logic is flawed. You just made a logical fallacy of the questionable cause variety - Post hoc ergo propter hoc.

Chronology does not imply causality. If you don’t understand this, then clearly there is no hope for you.

[timigod]

USING FLUTTERWAVE TECH does not equal YOUR MUMBO JUMBO RETAILER WHOLESAILER ANALOGY.

[kananga]

@timigod

USING FLUTTERWAVE TECH does not equal YOUR MUMBO JUMBO RETAILER WHOLESAILER ANALOGY.

Okay!

I see that we are beginning to accept "small small’ that PayStack is using FlutterWave tech. Progress.

[SkweiRd]

@kananga But 5 hours ago, @FatherMerry clearly stated that they used Flutterwave as one of their gateway options for a while:[quote=“FatherMerry, post:32, topic:9567”]
We used FW as one of many gateway options for a short period of time, and this was largely as a result of a bank relationship. Comments like this are the reason why there seems to be some public “animosity” between companies that should be working together.
[/quote]

So I’m not sure what your point is with this one. Anyway, I think this thread has been derailed enough. All @ekemini wanted to know was why businesses with responsive web apps still create mobile apps. If you want to fight on @iaboyeji’s behalf over whether Flutterwave powers (present tense) Paystack, then create another thread for it.

Thanks.

EDIT: I see @xolubi has started another thread to address the matter. Go and continue your bickering here: Is Paystack essentially a reseller of Flutterwave's excellent payment tech?

[Sherrytums]

@kananga you sir are seemingly being obtuse, intentionally. Makes some of us wonder why.

[kananga]

@Sherrytums

you sir are seemingly being obtuse, intentionally. Makes some of us wonder why.

How do you know I am a Sir? You a sexist? A misogynist? Lacking in social skills? or just obtuse?

[mark]

App is important and great. Hotels.ng has a mobile app. Compared to the resources required to maintain and update and promote a mobile app, apps don’t bring a lot of money. We have limited cash, need to make choices, so though we have an app, we don’t promote it, as we are more focused on web.

[somtoifezue]

Mark has spoken! Nothing but pure logic

[spokentwice]

@mark’s position reinforces my perspective:

@spokentwice

the most important decision a good CEO needs to make is what drives revenue - not what makes it look good

[ekemini]

Yak emem odu ke isong… Thanks

[leslie]

@FatherMerry

Comments like this are the reason why there seems to be some public “animosity” between companies that should be working together.

Coughs loudly

[doctorfox]

Geez…
Nigerians I hail thee. Sometimes I can’t help but wonder what the difference is between the privileged and the ones considered less.

But I digress; back to the origin of this post.
If I was to make a choice about creating a mobile app what would I consider?

1. Cost of building + maintaining app vs Cost of user acquisition + Lifetime value of user
2. Location of target users + computing power required to use the platform
3. The top apps with the highest number of install in my category or a similar category.

That for me would help my decision on whether to build for the sprints or not.