Fair enough.

I'd say it's kind of a good time to get into Android Development - Kotlin and Compose has made it highly pleasant and productive when compared to the days of Java and Views.

The answers about getting started with Kotlin and Compose are good, but I'd like to offer for your consideration that your app may actually be more appropriate to build as a website. Food for thought.

I didn't graduate from university.

In order to get some more money, I decided to take a TA-position at the school.

For context, I live in Sweden - university costs nothing to attend here, and you get access to a mix of governmental assistance and near-zero interest loans (at about 1/3 assistance 2/3 loans) to finance your living costs while attending university. To get this money you are required to get passing grades in a certain percentage of the courses you take, around 75% is required). If you do not meet these requirements, you lose your benefits, and quickly risk not being able to afford food and rent.

This TA-position however took up more time than I thought it would, and as such, I didn't manage to pass the courses I was taking. Since I no longer met the passing grades requirement, I could no longer get student loans and assistance, meaning that I had to keep working TA gigs to stay afloat. This finally became untenable, and I decided to drop out and move to another city and look for work.

So far, it's worked out extremely well. I've been ridiculously lucky.

Attempted homicide with a vehicle should probably carry a prison sentence along with a permanent loss of the privilege of driving said vehicles.

In my native language we say the equivalent of 'one and eighty-five' to refer to 185 cm of height, so basically we give it in meters.

deleted by creator

You can't deny that it correctly predicted the most likely token in this case.

deleted by creator

What level of Early Access would you call this? On a scale of "dev needs more money before the proper launch" to "basically done already and early access as a form of marketing".

I'm gonna give this one a shot. Thank you!

See https://youtu.be/w5GmDRW975g

Sure, but why would this lead to a decrease in power consumption? I'm not sure that follows.

Finally all that power won't be wasted waiting for a single app download to finish and install.

Wait, what do you mean by this?

I honestly stopped caring a long time ago. I've been using bluetooth headphones exclusively since before the jacks started going away, and I'm just not bothered by it.

It would have been nice for them to stick around, but it's not really a hill I'm willing to die on.

Just made for a good border-point, really.

This is all imagined though as I refuse to recognize the sovereignty of Finland and Norway - long live the Great Swedish Empire

Locally produced, artisanal airplanes.

A switch statement is probably a decent option here, yeah. You trade off a little bit of memory for what might be a few more instructions executing the switch statement, unless the compiler picks up on it and optimizes it. Maybe check godbolt for what gets generated in practice if you really care about it.

A few things come to mind:

1. The array is probably fine. It's not going to be particularly large and lookups are O(1)
2. It's a bit weird to me that you're using the char pointers as indices. I would probably use actual indices and spend the miniscule amount of additional stack data to improve the clarity of the code
3. You could save on some indentation by returning early instead of nesting the for-loop inside the first if-statement
4. Is the call to the lookup-table really safe? Maybe checking that the token from RNA is within the bounds is the way to go?
5. The only thing I would even remotely care about with regards to performance is the malloc, and that's not that big of a deal anyway unless the length of dna is really large. Streaming the result or overwriting the presumably already malloc'd input would be the only thing I would touch, and only if I could prove that it improves performance in practice.
6. (added in edit): if you can guarantee that the input is well formed, you can omit the bounds check and save some effort there.

The Matrix at 7 years old messed me up a bit, what with the whole mouth melting together-scene and all.

I've been enjoying Ventusky for planning for rain gear when cycling. It's been good so far.