One of my main motivators for building FoodNoms (I'm the indie app creator) is to offer something that allows people to not have to worry about how their data is being used or shared. No ads and no account/username/email/password/etc. Food diary data and goal metadata are all stored on your personal iCloud account.
Thank you - I found the nutritional information scanner in the "quick entry" screen but completely glossed over the barcode scanner icon in the food log!
I'm the independent app developer building FoodNoms. Thanks for the shout out and I'm really glad you're enjoying the app.
The app is truly a labor of love and it means a lot when I hear others are getting value out of it. If you or anyone has any feedback regarding the app, I'd greatly appreciate it.
You cemented my loyalty when you added the "turn anything that's a fractional-serving into an entire-thing" feature back when I asked about it a few years ago. :D
I absolutely <3 CodeSandbox. I’ve been using CodeSandbox for the past six months or so and it’s been a game changer for two things: (1) onsite frontend interviews - no more waiting for npm installs or worrying about node compatibility and (2) quick create-react-app prototypes - and if I get far enough, I simply download the source and continue to work locally.
I definitely think there's demand for solutions like this. I probably would like this even better if it worked on top of an existing static-site generator platform like Jekyll or Gatsby.
I just wrote about immutable deployments with Ghost 1.0, which is also open source (MIT licensed), and how that can be a nice compromise between static sites and hosted CMSes: https://ryanashcraft.me/ghost-and-now/
I might've tried Publii out if I had heard about it beforehand, but right now I'm really happy with the entire Ghost editing and consumption experience I've set up (thanks to the Ghost and Zeit teams).
Awesome post Ryan, I really like your approach! I just found out about now.sh the other day, and found its features and capabilities to be very exciting, and pretty unique for the most part. Does Ghost still have the capacity to output static html (thought it did pre 1.0; not sure with latest) ? If so, can I ask why you didn't go with using that feature, and then push the html via now or to any other service, since you're composing/editing locally anyway? Also, I looked for the ability to make this comment on your blog post itself, but didn't see any facility to do so, and then realized that this was because it's a read-only Ghost instance as you described. Is there any way to get comments with this approach. I'm thinking with the an Ghost-to-html approach (if available still in 1.0), you might be able to script something up to also embed Disqus into the outputted HTML, but as far as comments with your read-only Ghost on now.sh approach, no way to incorporate comments, correct? Anyway your blog theme was pretty attractive on Chrome mobile BTW. Enjoyable read all the way around.
Thanks! Great questions. I’m not 100% confident about supporting static generation and Discus integration with Ghost 1.0, although I imagine it’s feasible. That said, I’m personally not interested in pursuing either for my own blog at this time. Maybe in the future.
Sure. I'll also throw in a pointer to my React/Redux links list, which contains links to high-quality tutorials, articles, and other resources for React, Redux, ES6, Webpack , and related topics. Specifically intended to be a great starting point for anyone trying to learn the ecosystem, as well as a source of solid info on more advanced topics:
That's what we do. It's an OK workaround but ideally `connectRequest` would support multiple queries. Another workaround is to manually dispatch `requestAsync` actions, which might be necessary if you need to chain the requests.
Yeah server-side rendering hasn't been a focus for us. Currently, I don't think it is a great solution for server-side-rendered apps. I'm not exactly sure how much it would take to improve things here.
Author here. I totally agree if you're starting a new project or have the bandwidth to migrate to GraphQL – definitely consider it! However, I still think we'll need solutions that work for apps that use non-GraphQL APIs.
We're looking for talented front end engineers to help build out our analytics offering, engineers who aren't afraid to tackle the challenges of building out features for an evolving product.
Our front end stack is constantly evolving to keep up with best-in-class technology. We're currently building our UI using React and Flux. As we grow, we believe it's important to continually evaluate and improve our stack and take advantage of new tooling and libraries. We're looking for experienced front end engineers that are not afraid to try out new technologies, and that aim to constantly raise the bar for technical excellence.
About Amplitude
Amplitude provides mobile analytics that help companies leverage data to create explosive user growth. Anyone in the company can use Amplitude Mobile Analytics to go all the way down to the raw data and pinpoint the most valuable behavioral patterns within hours. Built on the industry’s most scalable platform, Amplitude ensures that customers never have to worry again about increasing data volumes or surprise bills. Founded in 2012 and backed by Benchmark, Amplitude is the fastest-growing analytics company with thousands of customers who are creating outsized competitive advantages with user behavior data including Nokia, Rdio, Rhapsody, MapQuest, DoorDash, and Yik Yak.
