Hacker Newsnew | past | comments | ask | show | jobs | submit | tfranco's commentslogin

So, they do analytics looking only at the database data?

I wonder if they built the analytics system themselves or are using a COTS.


You can still do analytics client side without the use of cookies. You just lack the view of a user and a session sice the cookie holds the primary key used to tie events into a session. You are basically just dispatching page views and events. Your reports will not look great but it's possible and probably will be a nice complement to a server side analytics solution.


That domain needs a digital certificate.


Quarantine is killing me. I really need to stop eating beans...


They spelled aquihire wrong.


That will prob. only happen when something similar to the google glass can last more than 30 minutes on one battery charge.


Allow me to disagree. :)

I've worked on low budget one man shows. Nevertheless I did TDD all the way and, I still wrote my cap scripts to deploy and asked the client to validate the implementation was right.

You might not tick all the boxes on the list for one man projects, but you can definitely do them with a team of two.


That's exactly the opposite of what I say in the post :)


Shameless plug :)


Amir, thanks for following up. Like I said in the article, I've used RubyMotion in production in the past. We were one of the early adopters and launched at least half a dozens apps in it. We payed for all our licenses. I love the product and this was money very well spent. It allowed us to use the same language (Ruby) in a larger portion of the projects. This was particularly important when some of our clients were small startups with an existing Rails app, and it was important for them to keep the same language for the mobile app.

I just think the support for Android should have happened a lot sooner. But of course this is easier said than done.

Moving forward to React Native is part of the same approach. It's important for us to use a technology that delivers fast in multiple channels and has a great chance of still being relevant in the next 10 to 20 years. And for me, these are the strongest points on Javascript.

And you're correct, React Native is not truly native, but it does the job pretty well without major impacts on usability. RubyMotion is truly native and very well designed IMHO.

Best of luck for the future.


I totally understand the need for Android support back then (and to your point should have happened sooner).

With regards to relevancy, RubyMotion is built on top of LLVM. With regards to Ruby the language itself, it's been around for decades and won't be going anywhere (granted the same can be said for JavaScript).

I'm waiting to see how web assembly will shake things up.

Best of luck to you man (I genuinely mean that). And if you ever decide to come back to RM, I'll be here to help :-)


Thanks. Same here. I truly respect the work that has been done on RubyMotion. Like I said in my post, brilliant people there.


We're on the verge of baselining a reference architecture in JavaScript for all our projects. We did the research with parity of features that already exist in Rails (Rails Admin, Devise, Sidekiq, etc).

You might not need a year to, at least, get my thoughts on that.


Do you mind sharing what back office solution you guys found?

Did somewhat the same kind of research for our projects, but unfortunately didn't find anything decent that could really compete with ActiveAdmin/Rails Admin/Trestle in terms of features and maintenance…



Ah, didn't realise there is a blog article about it. Thanks!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: