I think as long as it is a fun project (and not for real world applications) such experimental design is just fine. But yeah misclicking due to popups or other stuff is always annoying.
I can share a bit on this one.
I’m doing hybrid apps for the last 8 years and stick to Cordova on my day job but also tried Flutter and RN for a bit.
As I’ve seen some other comments about the iOS/Android look and feel (swiping gestures, etc.), Ionic (or the Cupertino package in Flutter) is the way to go. Without this, it would be a lot of trouble. However, as the recent iOS 26 update has shown, neither Ionic nor Flutter is going to support the new liquid glass design (yet). Since we never went with “our app must exactly match the (apple) design guides” this is not a problem for us but I’m sure others would love to be able to adapt the new liquid glass style.
I also never heard of any app being rejected due to being a hybrid app or not having the correct look and feel. Of course, you might see/feel that it’s not a native app but who cares.
Back in the days we even used a OTA plugin (it was a MS plugin, don’t remember the name) to automatically ship new .js/.html files without going through the review process. If I remember correctly Ionic still provides something like this.
When it comes to native stuff it get’s tricky. As always it really depends on the use case of the app. In our case we develop a navigation app using a native SDK to show a map + turn-by-turn nav + offline maps etc. This is probably the most non ideal use case for a hybrid app. We developed a few plugins to share data between js /native to initialize the map etc. However, the idea of sharing business logic is long gone. There’s so much stuff that’s happening natively and each time we implement it on Android, we have to switch to iOS and implement the Swift version of it.
Some others have also mentioned that a single person now has to know three platforms (iOS, android and Cordova (in our case with ionic + angular). This is true and the real downside. I’m quite familiar with iOS and android yet I’d never call myself a native iOS / Android developer. Yet, I’ve to write so much native code regarding permission handling, geolocation, threading (Ui/non-ui) and there’s always a ton to stuff happening from version to version (e.g. 16 KB Page Size on Android, iOS support for rotation the device/adaptive layout on iPadOS, etc). This is where a lot of time is lost. And the time is not only lost there but also with unmaintained outdated community plugins you suddenly need to understand and fix.
As a corollary, working with RN quite a lot, we just built an app for a client that was end to end finished and fully approved to both apps in a month, including pretty deep feature work and redesigning multiple screens. It includes the latest liquid glass native UI as well.
RN is a mess to get into, but once you've found a good stack you can really fly. We are working on a starter kit based off our experience that I think should represent the best possible starting point once it's released sometime before the EOY.
> You may be held up by a problem in a dependency such as poor documentation. It is tempting to start filling in the missing docs, but try to resist that temptation. Better to make minimal personal notes for now and, after you’ve made good progress, considering scheduling time to contribute some docs to the dependency.
I agree with most of the article, but this part keeps me thinking. Scheduling to contribute later will almost never work. Either I do it now or never. The task is lost in a list of infinitely many tasks. Also, contributing to a dependency (if I understand this correctly) is always something that helps at least two: yourself - doing something good, helping to improve someone’s work, getting something done - and the person who works on the dependency project. The other gets (positive) feedback and knows someone uses their product/software/library
I try to think in terms of owing the dependency a contribution as a small payment for using it, and this bugs me until I do it. But, sure, better to contribute docs sooner rather than not at all.
(One advantage of deferring is that the contribution may be better quality when I've had more experience of using the dependency.)
Native apps can in many ways be better than web apps but they definitely lack the client side control that a web app (or any website) comes with.
The user is sadly just a consumer and the product at the same time without an opinion.
What I also don’t like are companies that more and more push the user into using the native (I.e. installed) app over the website. I use almost all apps in browser (YouTube, LinkedIn) and the LinkedIn website has a “this content is only visible in the LinkedIn app” banner that is so prominent, it’s disgusting. You’re unable to see details of people changing their job / completing a degree and you’re unable to see the list of “visitors of your profile” (even though this is a silly feature).
On iOS I use YouTube in the browser for a single reason: ads are not shown and/or skippable by reloading the site. Sometimes I use the YouTube app on an iPad and the advertisement experience is so bad. I highly recommend using YouTube in browser (Safari).
Since I’m also somewhat addicted to short, but only use YouTube, I’ve built a chrome+safari extension that allows me to watch X shorts (for longer than 1sec) before closing the page and redirecting me to a different page (whatever you want). This is quite helpful.
You can check it out [here](https://chromewebstore.google.com/detail/youtube-shorts-trac...). I also use it on iOS via the Safari extension but I haven’t published it yet.
Cool product and great landing page. This is quite off topic: how did you make the code animation in the Feature Flag as Code section? I reminded me of prezi.com (with their slide animations). Would love to know!
I called this Opportunity FOMO for myself. I always wish to jump on the bandwagon with the next idea/project instead of sticking to the one I currently work on.
I decided for myself that there’s no need to buy a domain up front. I don’t even let myself look for potential domain names or start asking ChatGPT to provide me with some naming ideas. Most of the time, the project don’t even reach MVP state. During development and research I also learn more about my project and similar products thus helping me decide on a good name.
I agree that there's no need, and that yours is the reasonable approach.
That said, I often have project/product ideas at times when I cannot work on them. In fact, always. But I enjoy noodling on names and branding, and if I come up with a really good name that's available in .com, I register it.
I have revived project ideas 15-20 years later, and have been happy to have a great domain for it which would absolutely not have been available "now".
Of course I have many more domains that are patiently awaiting their prioritization.
The registration fees add up (and I do feel bad about reserving them for myself, although I've given a few away to persuasive requesters, and I've sold a few which, in aggregate, more than cover all of the registration fees).
I think that the problem is not that you lose momentum but rather that you start with momentum. I prefer having a clear mind and no need to rush (this happens when I’m excited about the project / have the initial momentum). This helps me a lot at deciding what I want/need/should/must do and what not. It also helps me to prioritize the project over/below family, friends, and house.
It helped me a lot that every time a have a new idea or want to start a new side-project that I wait at least two days before I dig deeper and get really started. Only then I really know if I really want this or if it’s just the initial hype/momentum.
