ceeK

I ordered an Addison Lee to the airport a few months back. The driver spent the entire time chatting about Uber and how dangerous it is. It's like they get off on it. He was also being quite racist about their drivers. This was at 3am in the morning.

This is just one data point, but I wasn't impressed.

They're probably using several bloated SDK's within their app for core Google services, view elements etc etc. If they're using dynamic linking, they have to include these in the binary even if they only use a small percentage of the libraries.

That's potentially one explanation.

Maybe it's just my experiences (iOS development interviews), but whiteboard interviews are actually quite rare. Most of the time it's either questions about iOS, pair programming iOS or discussing your implementation of some coding test.

I wonder if this is just a result of it being a more niche skill set than a general software developer.

According to discord (https://discord.engineering/using-react-native-one-year-late...):

  Unfortunately Android devices have much 
  greater variance in performance and tend to trail significantly behind iOS. 
  We were able to get our app running fairly quickly, 
  but the performance — specifically on touch events was not at an acceptable level even on higher end devices. 
  In addition at that early stage there was still a lot missing in the React Native Android feature-set that would
  have made getting our prototype to production level more time consuming than our iOS effort.

This was posted on the 7th June admittedly. Does this still hold true?

Thanks for the input. I do feel more and more that cross-Platform is a illusion like you say.

I already know Swift. Do you think Kotlin would a better transition into Android than straight up Java?

I've heard performance problems.

I think mainly for minor parts.

From my initial research it appears the React Native on Android suffers performance problems. I.e. the Discord app on that showcase is still native Android, whereas their iOS app is React Native.

What do you do as your day job? Do you find that you don't focus on one thing as part of that?

I'd say I'm the opposite. Funnily enough, I'm envious of people who are a jack of all trades because they can choose the right tool for the job. I just do iOS development in my day job and side projects and although I love app development, I find the lack of knowledge on other tools limiting.

Same here. I wonder whether this experience with the free cracked version helped make Photoshop any more popular. If it was only used in the legal sense, costing hundreds, would it be so popular?

Fantastic idea. Disappointed I can't use it now! I'll be waiting for use with Swift.

Black Swan Data | London | Full Time | Onsite

Black Swan creates better outcomes through technology and the power of prediction. We work with some of the world’s leading consumer-focused brands including Vodafone, Pepsico, Disney, Panasonic, Tesco, GSK and WPP. We've been named Britain’s fastest start up by The Sunday Times ranked #1 in their inaugural ‘Start Up Track 15’.

Variety is the spice of life here - one day you can be working on a startup project and the next on a project with over 1.1 million active monthly users (that is 99.9% crash free – not that we like to boast!). But if that’s not how you work, we are happy for you to take ownership of a project too. We work in an agency but it’s not all working at top speed, we also work smart. We use GIT flow, we love CI and our code has high unit test coverage. Nothing is getting into a build without a pull request.

We're looking for an:

iOS Developer (Junior to Mid-weight): Have a passion for pushing mobile technologies to the limits and want to work with our team of talented developers to build our apps that are used by more than 1 million people per month? Apply here: http://www.blackswan.com/blog/job/ios-developer/

Contact [email protected] for more information, or check out our website http://www.blackswan.com

You do have a good point, and something I didn't explicitly notice before. This does seem to have the indirect consequence of enforcing some sort of type information in the variable name, but I expect many iOS developers do that regardless.

It'd also be interesting to see the impact on readability when you have longer variable names. `point` definitely makes it more concise here. But if you had several points within the same scope, readability may suffer given type information is typically at the end of a variable name?

  path.addLineTo(childViewTopLeftPoint)
  path.addCurveTo(childViewTopRightPoint, withControlPoint1: arbitrary1Point, andControlPoint2: arbitrary2Point)

  path.addLine(toPoint: childViewTopLeftPoint)
  path.addCurve(toPoint: childViewTopRightPoint, withControlPoint1: arbitrary1Point, andControlPoint2: arbitrary2Point)

I feel the second version here allows me to bypass obtaining the type information "..Point" from the variable name when reading.

Interestingly, I wonder how this type of method would be converted:

  addArcWithCenter(center: CGPoint, radius: CGFloat, startAngle: CGFloat, endAngle: CGFloat, clockwise: Bool)

You'd perhaps think of addArcWith(center: CGPoint), but then you'd need to have 'center' in the variable name to convey meaning. Keeping addArcWithCenter maintains obj-c status quo. addArc(withCenter: CGPoint) is more Swifty, but you may have repetition if your variable is named centerPoint, or similar. I have a feeling it would be kept as is.

To be honest, even as a fairly seasoned iOS developer I still prefer to have a non-optional first argument in my APIs.

Whereas the post's example compares:

  path.addLineToPoint(CGPoint(x: 100, y: 0))
  -- to -- 
  path.addLineTo(CGPoint(x: 100, y: 0))

I've been doing it as so:

  path.addLine(toPoint: CGPoint(x: 100, y: 0))

...requiring the "toPoint", which can swapped out true method overloading style:

  path.addLine(toArc:...)

In your internal method implementation, Swift allows you to replace the external method name with an internal one, so that it's still nice to work with:

  func addLine(toPoint point: CGPoint) {
  ...
  }

I personally think it's a lot more readable. Otherwise the first argument has to have a really descriptive class name (recommended for sure, but often not the case).

First of all, it looks great, so well done for that! It's fantastic to actually make it to the release stage.

That said, I'm a big fan of adopting the best design paradigm for the platform. If I was building an Android app, material design would be the go to. Why? Well, Android users have already used it. The cognitive burden to how things feel and work has been removed, letting your users feel familiar with the app from the get go.

Similarly, with iOS, closely following their human interface guidelines will produce the best results for allowing iOS users to immediately feel at home in your app. This sentiment is mimicked in the WWDC2014 video Designing Intuitive User Experiences.

For this reason, I'd personally tend to shy away from trying to port design principles to other platforms. It sure looks nice, but is it worth it?

I suppose it could be referencing the fact that the mother buys the games and allows her kids to play them. Making an enemy of her means no game time?

Glanced down the website and although it looks cool, I didn't get what problem the product actually solves, or why I'd want to have one.

I posted an offer to HN to build their app for £100. Monetary value is obviously very little, but it's a token gesture that technically gives you freelance experience.

It was great to build my portfolio up; I'd recommend it if possible. It's much easier to land gigs with a freelance portfolio.

https://news.ycombinator.com/item?id=6382405

SEEKING WORK - London, UK & Remote

Hi I'm Chris - an iOS developer and designer looking for work.

How can I help? I love building well crafted iOS applications, and have been doing so for 5 years. I deeply appreciate thoughtful design, which I put forward in all my work. I build apps with backends from conception to App Store, and have helped guide my clients to release and beyond. Any type of app you need, I can build it, and I can build it well. Above all though, I'm a friendly guy who you'll enjoy working with!

Previous client: "I've had the distinct pleasure of working with Chris for my first ever iOS app and I can honestly say that he has made the entire experience fun and exciting."

I'm currently working on my own startup [1], backed by a VC at Balderton Capital, which is currently being consider for App Store promotion. I've been part of a team whilst they were taking part in TechStars London, and I'm incredibly active in this space. I'm currently looking for a gig to further my startup's runway. Moreover I have been through the EF accelerator last year, which aims to take the best technical people Europe wide and get them to found startups.

Portfolio/CV: http://www.chrishowell.me

Email: [email protected]

[1] https://itunes.apple.com/gb/app/fitter-find-book-best-workou...