smweber | 2 months ago | on: The Gleam Programming Language
smweber's comments
smweber | 2 years ago | on: WhatsApp Chats Will Soon Work with Other Encrypted Messaging Apps
smweber | 11 years ago | on: Dash now available on iOS
smweber | 12 years ago | on: Alcatraz – Package manager for Xcode 5
smweber | 12 years ago | on: Starting Feb 1, new apps and app updates must be optimized for iOS 7
Apps that are built for iOS 7 get the new shiny keyboard and some different behaviour when run on iOS 7, but can still run fine on older versions of iOS if the app developer is willing to support older versions of iOS. This is done by setting an option called "deployment target" to an older iOS version when building in Xcode (and testing a ton on older versions of iOS, and not calling newer APIs on versions of iOS that don't support them).
So this announcement means Apple is dropping support for older versions of Xcode (with older iOS SDKs), but older versions of iOS are still technically supported as long as you're building with the iOS 7 SDK.
smweber | 13 years ago | on: Light Table 0.4 released
smweber | 13 years ago | on: From Idea to Execution: Mantaphrase's Japanese Heritage
smweber | 13 years ago | on: Show HN: I spent two years working on an HTML5 game. I finally released it
smweber | 13 years ago | on: Stripe in Canada
smweber | 14 years ago | on: Startup escape path
smweber | 14 years ago | on: In defence of Objective-C
smweber | 14 years ago | on: Google account gets blocked without explanation
I think this time I'm going to actually do something. Probably not ditch Google entirely, but ensure I'm not entirely dependent on them.
smweber | 14 years ago | on: Show HN: My weekend project: Scrollendar (for iOS)
If sales actually pick up on iPhone, I think it'd be a good project for me to learn the Android SDK.
smweber | 14 years ago | on: Show HN: My weekend project: Scrollendar (for iOS)
I'm hoping to get some feedback on my second iOS app, Scrollendar. My first app, LessonLog, is pretty niche (teachers with iPhones), so Scrollendar is my first app that I feel has a chance at any kind of popularity.
Some background: I finished Scrollendar v1 and got it on the App Store last May. The first version only took about a week to build, and although I was fairly happy with it, it had some rough edges. Having an engineering background, I figured I'd leave the marketing until after I submitted a few updates and got things a little more polished.
However, I made two assumptions that (unsurprisingly) turned out to be false:
1. I greatly underestimated the amount of time needed to fix the rough edges and be really happy with the final product. I ended up adding the scrolling day view, which ended up being a lot of work, then I rewrote the entire backend due to deficiencies in NSDate and EventKit. What I figured would take a couple weeks took over a month.
2. I greatly overestimated the amount of people that would find Scrollendar without any marketing. I wasn't expecting many people to find it through organic App Store searches, but I figured at least one or two people would stumble on it each day. What actually happened is after an initial spike of six whole downloads the first day, the daily downloads quickly dropped to zero. I haven't had a single purchase in the last 30 days. This is even less than my niche teaching app LessonLog.
So I'm hoping to get some feedback on the app and the website (scrollendar.com). I'd also love any tips for a first time mobile app marketer. I've poured over every HN post that has anything to do with online marketing, and most of it comes down to: - have a viral component to the app (not really applicable to Scrollendar) - build a following online with a well written blog and great social media posts (I have neither right now) - build a great website with lots of useful content (like bingo cards) to drive search traffic (again, not really applicable)
So basically, my online marketing plan boils down to: e-mail mobile app review sites. Is this sufficient? What else can someone in my position do?
Thanks in advance! Scott
smweber | 14 years ago | on: A lesson on the importance of encouraging your children with their projects
But most of all I think the overall simplicity of the language is really what’s standing out to me. So far I think the lack of ad-hoc poly and macros are a plus - it really reduces the impulse to write “magical” code, or code with lots of indirections. In the past I’ve definitely been guilty of over-abstracting things, and I’m really trying to keep things as simple as possible now. Though I’ve yet to try Gleam with a large project - maybe I’ll miss the abstractions as project complexity increases.
I suspect Gleam will be a great language for small to medium sized projects written with LLM assistance (NOT vibecoded) - the small language, strong typing and immutability gives good guardrails for LLM-generated code, and encourages a simple, direct style of programming where a human programmer can keep the whole structure in their head. Letting an LLM run free and not understanding what it’s written is I think where projects run into big problems.