I don’t understand. People are willing to pay around ~$50 every month for netflix, Spotify, HBO, etc. Yet programmers are debating if subscription are ok and people will be able to pay. If I’m able to pay $$ for my entertainment then I will be able to pay monthly for software.
Rice fields at the delta de l’ebre river in south Cataluña.
If everything goes well, Bilengua will have its video ready in less than 24 hours. 💪🏃🏃🌪🎬
I’m building an app with Swift 3 and running on Apple Watch. It’s been so much fun and a great way to dive deeper into some of the specifics of watchOS SDK. Also, a great way to improve my Swift 3 knowledge.
Since the app isn’t finished and I don’t have a permission to talk about the code, I will leave that part for some other time. Today, I would like to write about my experiences managing the project, working with watchOS 3 and testing the code on a device.
- Before you commit to a feature, check the limits of the watchOS SDK. It doesn’t matter that it might sound basic or if features like that already exist on iPhones. WatchOS is a different story and there are lots of limits you need to be aware of. Read the documentation before writing code.
- Writing apps for watchOS is slow. Allow yourself at least twice as much time as you normally would for iOS testing and debugging.
- I’ve lost the whole day trying to debug code on a watch and nothing worked. If possible, keep testing the app on the simulator. If you have to test it on a watch, be aware of the fact that you might need to reset your watch from time to time.
- Keep in mind that Apple Watch is a companion to the iOS app. It means two things. First of all, most tasks (entering data, signing in, enabling features, etc.) should be done on a phone. Secondly, you will need to build a robust iOS app in order for your Watch app to be functional. That means that the time and the effort you need doubles.
- Be aware of changes and obstacles. Remember that you’re working with a maturing platform and using a language that might slightly change in a few months. SDK’s available for watchOS 3.2 might not be there on the next version of the platform. Also, current limits might be lifted by a new SDK.
Last but not least, keep releasing builds. Like with any other platform, it is easy to focus on bugs and limitations without getting enough feedback about the overall direction. This is something I’m definitely guilty of.
I did some research and cheap wine (even from Spain) does affect your next day productivity quite a lot … 0_o
Sending “Hey, I was able to solve the issue and everything works as we discussed now” message to a client feels really good!
iOS Programming question: Is it possible to send an email (use SMTP protocol) directly from an Apple Watch? I tried using WCSession and send emails on a phone (via SendGrid)… but I’m hitting certain limitations of WCSession during the connection.
While preparing for our September’s half marathon, we did 14km last week. Running around Tarragona is always fun but this aqueduct was definitely a highlight of our day.