TomTom Sports | Mobile Developer (React Native, iOS, Android) | London, UK | Full-time, Onsite, https://www.tomtom.com/sports/
Would you like the chance to work with React Native in Central London, to the backdrop of panoramic views of the capital? Somewhere where strapping on cutting-edge sports wearables and venturing out to Regent's Park can be a valuable part of your work day if you'd like it to be?
If you're a strong native iOS or Android developer with an open inquiring mind when it comes to learning new tools and ways of working, get in touch! We're growing our team for the long term and are open to great people of all experience levels.
I note this from Pebble's developer blog, suggesting that a Fitbit-targeting successor to Pebble's app SDK may be a big part of the plan:
"Although this chapter in Pebble’s developer story is closing, our team and ethos have found a new, welcoming home at Fitbit. We can’t wait to have you alongside us for this next adventure. Third-party Pebble developers have a massive opportunity to drive how a Fitbit developer ecosystem will take shape. We hope you’re as excited about seizing this opportunity as we are.
Over the coming months we will be working closely with our new friends at Fitbit, building the foundation for the next great wearable experiences. We want you—our fantastic developer community—to keep playing a crucial role in our success. More information will follow soon, so stay tuned!"
This sound like typical post-acquihire PR bullshit. New 'exciting opportunities' and 'building the foundation for the next great wearable experience' does not in any way imply that any useful thing resembling a smartwatch will be created. It doesn't imply there will be a developer-friendly platform.
Nor does this message actually make sense. "We want you—our fantastic developer community—to keep playing a crucial role in our success." There is no "us" and "our success" - they just got bought by another company and are shutting down the whole product line. They are literally a different entity now.
> This sound like typical post-acquihire PR bullshit.
Maybe, but of the major players in the smartwatch or not-quite-dumb fitness tracker markets Fitbit is notable in not supporting any kind of app/face ecosystem. Obviously there's a ton of stuff for the true "smartwatches" from Apple and the assorted Android Wear stuff, there's Garmin with ConnectIQ, the now-defunct Microsoft Band had an SDK for developing Tiles, and then there were Fitbit, Jawbone, whoever made those Bluetooth-connected bands that Aldi had one week, etc. with fitness trackers that have some predefined screens.
Purchasing the IP and hiring a bunch of the software developers from Pebble lets Fitbit probably cut 2 years off of the development timeframe for them to have devices with changeable apps and an ecosystem that lets them have third-party developers. They could undoubtedly get something out faster, but it'd be an immature product and would probably take them another year before it could really be considered good.
I fully expect to see a lot of the Pebble code to make it into Fitbit devices - probably not for a year or more unless they can do some things with the existing hardware, but a lot faster like this than by trying to staff up from elsewhere and develop it all in-house.
No argument over the phrasing. However, an evolution of the Fitbit Blaze device platform hooked up to something inspired by the CloudPebble online SDK doesn't seem implausible.
TomTom – http://www.tomtom.com — London, UK – Mobile & Embedded Apps and DevOps roles (full time, on site, relocation available)
We're TomTom's navigation software team in London and we create the best on-the-road experiences for drivers and bikers everywhere.
The apps we make are built into Renault and Smart in-car systems, available for smartphones, and at the heart of TomTom's expanding range of consumer devices where hardware and software are conceived together. Like the just-released TomTom Rider made specially for bikers: http://tomtom.com/en_gb/drive/motorcycle/index.html
Developers who join our expert team are valued for their ideas as well as their skills, and we encourage both through regular hack days, plus training or conference attendance in areas that interest them.
-- Role: Mobile & Embedded Apps Developer
Our apps feature TomTom's signature design language and map-centric UI, optimised for use on the road. Working with TomTom's UX team, app development with us is a challenging mix of custom UI development and deep routing, guidance, traffic and search presentation smarts. If you join us you'll be developing with Java, C++, JavaScript, Android, iOS and Qt.
-- Role: DevOps for Mobile & Embedded
Building scaleable CI infrastructure for mobile & embedded app testing is hard, particularly when you add custom pre-release hardware and gigabytes of map data into the mix. If you join us you'll be working with Android and iOS SDK command line tools and device emulators, Jenkins, Git, Nexus, Gradle, Ruby, Docker and a mix of local device farms and cloud computing services.
Developers who join our expert team are valued for their ideas as well as their skills, and we encourage both through regular hack days, plus training or conference attendance in areas that interest them.
-- Role: Mobile & Embedded Apps Developer
Our apps feature TomTom's signature design language and map-centric UI, optimised for use on the road. Working with TomTom's UX team, app development with us is a challenging mix of custom UI development and deep routing, guidance, traffic and search presentation smarts. If you join us you'll be developing with Java, C++, JavaScript, Android, iOS and Qt.
-- Role: DevOps for Mobile & Embedded
Building scaleable CI infrastructure for mobile & embedded app testing is hard, particularly when you add custom pre-release hardware and gigabytes of map data into the mix. If you join us you'll be working with Android and iOS SDK command line tools and device emulators, Jenkins, Git, Artifactory, Gradle, Ruby, Docker and a mix of local device farms and cloud computing services.
The developers who join our team are valued for their ideas as well as their skills, and we try to encourage both through regular hack days, plus training or conference attendance in areas that interest them.
--
Role: Mobile & Embedded Apps Developer
Our apps feature TomTom's signature design language and map-centric UI, optimised for our domain. Working with TomTom's UX team, app development with us is a challenging mix of custom UI development and deep routing, guidance, traffic and search presentation smarts. If you join us you'll be developing with Java, C++, JavaScript, Android, iOS and Qt.
--
Role: DevOps for Mobile & Embedded
Building scaleable CI infrastructure for mobile & embedded app testing is hard, particularly when you add custom pre-release hardware and GB's of map data into the mix. If you join us you'll be working with Android and iOS SDK command line tools and device emulators, Jenkins, Git, Artifactory, Gradle, Ruby, Docker and a mix of local device farms and cloud computing services.
I wonder if the teens who favour Instagram and Snapchat today will nevertheless age into people who get more out of Facebook as they get older.
When you're young, most of the people you know and think about are still right there around you and you see them almost every day. You haven't left too many people behind yet. But that changes quickly over time and an increasing proportion of the people you know and care about, the ones you met at a particular place and time in your life, are no longer close by. Being able to keep in touch with those people's comings and goings and relationships and family lives to the (relative) depth afforded by Facebook probably becomes more attractive and more valuable.
So although Facebook may be losing its original stomping ground to simpler, more targeted alternatives, perhaps both Facebook and its active user base are maturing together.
When Harlequin started out with Dylan, to bootstrap we first quickly morphed LispWorks into a high-functioning Dylan IDE. This was done through a combination of macro, reader macro and CLOS MetaObject Protocol abuse, allowing us to achieve a faithful rendition of Dylan's syntax and object system semantics respectively.
When Dylan went from prefix to infix syntax the reader macro indirection got all the more elaborate: what started out as a trivial reader macro that treated colons differently started delegating to a full-blown lex & yacc style parser instead.
All the better, most of this was achieved modularly: Lisp editor buffers and Lisp listeners would run happily alongside Dylan editor buffers and Dylan listeners, Lisp code could still compile load and run alongside Dylan code, and Lisp classes could interoperate cleanly with Dylan classes.
There's no question that Common Lisp and its predecessors are some of the most formidably adaptable and hackable programming environments ever created. Only Smalltalk really comes close, and they have complementary strengths I think. Standard macros, reader macros and a comprehensive MOP are some of the key things that stand out in Common Lisp's favour in that hackability comparison.
I've occasionally wondered if we should take the old emulator sources and re-package them as a separate repository. It isn't clear that anyone knows how to make them run any longer or whether or not they'd run on anything other than LispWorks or if this would be of anything other than a historical curiosity.
Looking back at some Dylan code again now, I still find its richer, Lisp-derived, hyphenated naming approach more readable-and-expressive than either camelCase or underscore_separated identifiers.
When Dylan switched from Lisp syntax this was something that was fretted over an awful lot, for obvious reasons, but we went with it and it worked fine.
I'd love to see some other algebraic (non Lisp) syntax language get more creative in this direction again one day.
Optimisation colouring was one of the Harlequin Dylan features I was most proud of having a hand in back in the day. Did anything like it ever get implemented in a more mainstream IDE?
We only implemented it for static optimisations I think (i.e. you could see at a glance how well the compiler had inferred types, resolved method calls, inlined functions, etc), but we had a lot of ideas at the time around its future application to profiling results, as well as layered, more interactive presentation.
Would you like the chance to work with React Native in Central London, to the backdrop of panoramic views of the capital? Somewhere where strapping on cutting-edge sports wearables and venturing out to Regent's Park can be a valuable part of your work day if you'd like it to be?
Come help us make the TomTom Sports app the very best of its kind: https://www.tomtom.com/sports/sports-app/
If you're a strong native iOS or Android developer with an open inquiring mind when it comes to learning new tools and ways of working, get in touch! We're growing our team for the long term and are open to great people of all experience levels.
https://www.tomtom.com/careers/jobs/Mobile-App-Developer_JR0...