whofearsthenight

joined 10 months ago
[–] [email protected] 1 points 9 months ago

It's not really because the developers are cheaper, it's because the vast reduction in complexity is cheaper. Let's say you've got a great general app idea and you're going to build a startup. Your app is going to have to be mobile and desktop. To do that well, natively, this means:

  • you're going to need a backend dev who are probably going to be building APIs that are touching on web tech.
  • You're going to need a developer team who can target Apple platforms, Android, and Windows. I lump Apple together here because although it's not entirely fair to say that it's as simple as they promise where you just click a box and your iOS app works on macOS, you're at least able to work in the same general toolset (Swift, SwiftUI, Xcode, etc.)
  • You're going to need designers who can design to the specific needs of the platforms, which is also going to mean more domain expertise.
  • testing for each of those platforms.
  • This is true regardless, but you're going to have to deal with more platform-specific support. More platform specific documentation, etc. How do you do think x on platform y? Where is the button on this platform vs that one?
  • maintaining feature parity as you continue to build is going to be much more difficult, and you're going to have to decide if you want to maintain feature parity and slow the whole process, or give up and launch on some platforms first (hopefully there is no one that uses a Mac and an Android phone or Windows and an iPhone or an iPhone and a Samsung Tablet or that gets annoying real fast.)

In short, moving from one platform to two natively doesn't double complexity and cost, it's far, far worse than that. It's not that a good web dev costs $70k vs an iOS dev that makes $90k, it's that a good iOS dev costs $90k, and a good Android dev costs $85k, and a good Windows dev costs $80k and one of those people hopefully is familiar enough with each platform to be the team lead so you can tack on another $20k for them...

And all the while you're building that team and building your 3 different platform native apps, a competitor or several will launch on Electron and web tech and take the market because no one except us nerds give a shit about whether something is using the right platform idiom or even knows what they are, and far fewer still have any idea how to check RAM usage and the like.

[–] [email protected] 6 points 9 months ago

Also, in a lot of cases, supermarket tomatoes are nowhere close to ripe. Supermarket tomatoes are generally garbage anyway, but if you can give them a day or two to ripen.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

You know, as an amateur with massive impostor syndrome who's probably going to be applying for jobs soon, this comment and those like it give me strength.

[–] [email protected] 1 points 10 months ago

Probably should have posted a pic with a good wheel.

[–] [email protected] 1 points 10 months ago

"somewhat" is doing a lot of work here. I mean, they didn't re-write the kernel, but you can google example of the UI pre and post iPhone announcement.

[–] [email protected] 1 points 10 months ago

The timeline is technically correct but misleading, and please google what Android looked like prior to the iPhone announcement. While you're there, might also want to check out the technical differences like iPhone prioritizing things like animation and user interaction. Wouldn't also hurt to check out the first, say, 1-4 Android devices compared to literally just the first iPhone and tell us which one our phones look like today. Also, do we think that Apple was just like "here's a new OS we made over winter break?" They announced in '06. Android was developed probably at a similar time, bought by Google, and then had to pivot hard after iPhone announcement, and harder still after hardware actually got into customer hands.

[–] [email protected] 1 points 10 months ago

Just about every invention is obvious in hindsight. Take a look at what Android looked like pre-iPhone announcement and then post.

[–] [email protected] 8 points 10 months ago

...with the understanding that It's often grounds for termination in which you won't even get unemployment unless OT is specifically spelled out in your contract this way. The term in these cases for "no" in which you're not being asked to break laws/regulation/contract, is usually "insubordination." Oh and company policy, though even that's sketch because company policy is sometimes dumb as shit so it will occasionally get overridden.

I'm not a bootlicker, join a union if you can, know your contract and don't do an iota more than what's required unless you gain a benefit from it, but always be wary of advice like "tell your boss to go fuck themselves!"