Offer HN: My experience in iOS app development
I've enjoyed reading HN for a while now, and I'm fond of the intelligent culture that seems to have evolved here. I have been looking for a way to give back a bit, and to expand my technical writing skills as well. This is as much for me as it is for you :) I have at least some expertise in this area, and I'm happy to share.
So if you have a question about anything iOS related, I'm willing to answer to the best of my ability. If you have a piece of code that's troubling you and you'd like another set of eyes on it, let me know. If you have an idea for an app and want some advice or direction, I'm happy to help. (I'm unable to agree to any NDAs in this case, but I would consider any communication private; nor do I have any intention of stealing any ideas. I have plenty of my own that I should be working on instead anyway!)
If you're interested in taking me up on this offer, you can comment here, or if it's more private, sensitive or just easier for you, you can email me at hn@pocketsevens.net. I'll reply as soon as I can.
13 comments
[ 3.0 ms ] story [ 40.5 ms ] threadAs for your second question, I'm never 100% comfortable about this, which is kind of fun. I never know what someone is going to ask me to do next, but the API docs are good, the community is helpful and it's a fun platform to work on. There's lots of answers out there if you need them. However, I can tell you there are important things to know. For one, memory management is vital on iOS devices. The OS can and will remorselessly kill your app for using too much, without warning. Memory overuse is a crashing bug, do whatever you must to squash it dead.
Is learning to code natively always preferred, or do you respect the idea of generalizing your platform?