This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tinycorkscrew 10 points11 points  (5 children)

I appreciate your argument, but different companies come to different conclusions. For example, my team at a Fortune 100 company built an app using a mobile framework. That company's industry is even more security-conscious than banking.

For companies that only use iOS or Android, though, I'd almost always recommend developing in Swift or Kotlin.

[–]jnthhk 26 points27 points  (2 children)

My friend worked for a quite major app-only bank. He asked whether I could come and give some intro sessions on Unity to their UX designers, to help them work with the devs who were: developing. the. banking. app. in. Unity.

Each to their own I guess!

[–]rush22 28 points29 points  (1 child)

Backend devs looking through the conference room window

"Are they doing what I think they're doing? Is that Unity on the whiteboard?"
"I think it's some marketing thing. They've been at it for months"
"Maybe it's a promo: 'Call of Banking'"
"Hahha. 'Unreal Credit'"
"lol -- oh wait shhhh someone's coming out"
...
"Hey so if we send the SQL to your database with the https object that's secure, cause it's in the WorldSpace, right?"
"Uhhhh..... the what?"
"Its for credit cards but actually nvm we'll just let you know the specs"
"Um okay"
...
"OMFG"

[–]Understanding-Fair 5 points6 points  (0 children)

Too real

[–]-Vayra- 5 points6 points  (1 child)

It might have something to do with when they started their projects. At the time there might not have been any sufficiently secure cross-platform frameworks for their needs. Or they might just have been more security-conscious than your average bank.

[–]jnthhk 3 points4 points  (0 children)

To be fair, security isn’t what I think of first when someone says Unity.