Weeknotes vol. 6: Web and hybrid and native, oh my!
(It’s Tuesday but I’m pretending it’s last Friday.)
I’ve gone back and forth on Native v.s. Web v.s. Hybrid v.s. Native v.s. ∞ quite a bit. There are pros and cons to all of the options, but, for the initial launch, I have officially landed on the following:
- Web app (Rails, baby!)
- iOS (Hotwire Native)
- macOS (A hybrid Swift app generating a web view)
- watchOS (Native, primarily for the voice to text)
(ducks from the lettuce, etc. that Chris is going to throw.)
This way, deploying updates is as easy as git push origin main (the cheeseburger of computers) and we’ll have minimal App Store risk. What this does mean is that we need an API for watchOS, which I took care of during the early part of last (this?) week. Though it’s the core of any modern day digital product, I had little experience creating an API and did run into a few gotchas around authenticating with tokens v.s. web logins and sessions. After wrapping my head around the issue I was able to read, write, delete, etc. from the API and had a very quiet celebration in my mind.
I quickly prototyped the native watchOS app to read, write, delete via the API and get an understanding of how this particular app will look and feel so we can understand our design boundaries. And what a good use of time it was. I quickly learned that the simple app I had in my head needed to be about 10x simpler to decrease the clicks it takes from open to posted due to the required native voice to text screens and interactions. I also learned how easy it is to get that sexy swipe to delete on the listing view.
Design for the Web/Mac app is underway and is really starting to look like something. This next week will be spent excitedly getting the working app in line with this week’s design progress and answering Matt’s questions on GitHub so we can finally toggle this codebase’s invincibility mode to the on position.
Like this? Get email updates or grab the RSS feed like it’s 2008.
More from the blog
-
The sorting machine: recruitment’s race to the bottom
> The sorting machine was built to cope with a genuine problem. Where it went wrong was in mistaking efficiency for effectiveness, in assuming that the ability to process resumes fast meant the ability to evaluate candidates well. The fix is not a smarter machine but a more modest one, paired with humans who are given the time, the tools, and the structured information to do what they were always better at.If you've been involved in any part of the recruitment process, the last 18 months have been dispiriting, to say the least. Hiring became a closed loop. Employers adopted applicant tracking…
-
Weighing smoke: why GEO dashboards are mostly useless
> The promise of a tool that gives you similar search visibility to the pre-agent world is understandably seductive. But before you eagerly hand over your cash for a platform, consider whether an afternoon's work a month might be a more cost-effective alternative.I recently wrote about [the GEO chimera](https://betterthangood.xyz/blog/geo-practice-versus-snake-oil/), the cottage industry promising to optimise your brand into AI answers. My argument was that the levers being sold mostly did not exist. Another part of the industry is selling gauges rather than levers. Estimates of the spend on …
-
Another nice mess
Somewhere in your business right now, someone is assembling a picture that no single app can provide. It may be the project manager pulling hours from Harvest and budget data from the finance tool to assess whether the engagement is still viable. Maybe it's you on a Sunday, because what you need is not any one number from a system, but the pattern across three of them. The cloud gave small businesses access to the best software they had ever had, priced monthly and built for specific purposes. But twenty years of sensibly chosen apps have left the average small business with a patchwork data …
-
The state and the machine
> What little we saw of Fable and Mythos offers both cause for excitement and concern. It was widely and credibly seen as a model of a completely different caliber from those that had come before. Perhaps the risks in this instance were overstated or amplified for political ends. What is more profound is that the short time we had with the models offered a clear glimpse of a future in which a single company is making significant progress toward a superintelligence with the potential to rival or exceed the power of nation-states or even massive corporations. That juncture was never going to ar…
-
We have ways of making you pay
> The true cost of AI work is hard to measure; the value of AI work is also hard to measure, and metering changes which of those two blindnesses you notice first. It drags the cost into the light, itemised and arriving monthly, while the value stays diffuse, lagging and easy to argue about. That asymmetry is exactly why the panic is showing up now, ahead of any definitive verdict on whether the spending was worth it.Simon Willison did the arithmetic on himself. He pays $200 a month across his Anthropic and OpenAI consumer plans, and when he ran the [ccusage](https://github.com/ryoppippi/ccusa…
