HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
turbolinks
turbolinks-ios
Swift2016–2020
turbolinks / turbolinks-ios · Archived

turbolinks-ios

Native iOS adapter for building hybrid apps with Turbolinks 5

6Distinct people
6Mentions
0Explicit recommenders
871GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Native iOS adapter for building hybrid apps with Turbolinks 5

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2016-03-09 20:06:31 UTC to 2020-06-25 17:38:16 UTC.

0122016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202

What Hacker News says

6 sources
Matouš Borák published a few interesting write-ups about the front-end: https://dev.to/borama/a-few-sneak-peeks-into-hey-com-technol... Basically it's a new, unreleased version of Turbolinks[1] + StimulusJS[2] The "native" apps are wrappers [3] for the webapp, but with some native integrations for navigation, etc. [1] https://github.com/turbolinks/turbolinks [2] https://stimulusjs.org [3] https://github.com/turbolinks/turbolinks-ios
In DHH: The HEY stack Vanilla Ruby on Rails, MySQL, redis, stimulus, elastic search
It's created by Basecamp which makes Turbolinks [0], Turbolink iOS [1], and Turbolinks Android (deprecated) [2], so there's a good chance that snappiness you're seeing is due to those awesome tools! (In fact, this Github issue comment [3] seems to confirm that HEY uses Turbolinks.) On a related note, really wish things had gone this direction. Instead, it feels like React, Angular, etc. re-created the backend in the frontend, so now for most apps you essentially have two backends plus one frontend to maintain. I think as soon as our frontends started requiring controllers and routes to work we should have been like, "Hey, wait a minute..." But I guess design folks tend to know JS, so I can see how that combo won. My $0.02 from 5+ years in the industry is that you probably don't need React, but Godspeed if you think you do - just maintain
Read the rest
extreme discipline or you'll end up with spaghetti code (esp. if contractors are involved) faster than you can blink. Long-term, I hope things move back to sanity. React and company work OK for some problems, but 95% of websites/webapps can probably get by with either straight HTML/JS/CSS or server-side rendering/templating. [0] https://github.com/turbolinks/turbolinks [1] https://github.com/turbolinks/turbolinks-ios [2] https://github.com/turbolinks/turbolinks-android [3] https://github.com/turbolinks/turbolinks-android/issues/111#... Edit: Formatting
In The Return of the 90s Web
You're wrongfully trivializing Turbolinks 5. The whole point of using it is so that you get an incredibly responsive experience without having to resort to bolting on a front end framework and maintaining essentially two application states. This is a huge productivity boost. Furthermore, the optimizations that TL v5 provides means that you can use your webviews for mobile and get an incredibly responsive experience. That is what they are doing with Basecamp and they're able to provide a first class mobile experience on iOS, Android, a desktop app, all with a team of 12 developers (https://m.signalvnoise.com/the-majestic-monolith-29166d02222...). That's fucking impressive. On top of that, they've release the generic iOS and Android wrappers so that you can roll your own mobile applications with Rails and Turbolinks. https://github.com
Read the rest
/turbolinks/turbolinks-ios https://github.com/turbolinks/turbolinks-android There's no other framework out there that remotely comes close to providing that value to the end developer. The market demands that your app be present on multiple platforms, which is usually a fucking nightmare if you're a small dev team. These Turbolink additions now give you a fighting chance.
In Rails 5.0.0.rc1

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.