RubyMotion is still alive?


#1

Hello everyone,
I know about the existence of RubyMotion for a few years, but I never use it or tested.
I am thinking to try RubyMotion for an new application in the company where I work.

I have been reading the documentation everything seems very interesting, and I really like the idea of Redpotion and Bluepotion.

But I’m worried about the community, the popularity of the project and the development.
Nowadays comparing RubyMotion with alternatives like ReactNative etc … what is the rubyMotion position?

I have not even been able to find RubyMotion in the list of recommendations in all new articles (newer than 2016)

All the examples on your website are 3-4 or 5 years old (which makes me think that there is nothing new since then or the project is stopped or nobody is worried about the project)

If you visit the page http://www.rubymotion.com/about/ there is nothing new since 2014 (4 years ago, which gives me an image of a very abandoned project).

In http://www.rubymotion.com/news/ I have not found anything interesting, I have only found 6 old news, some of them with a link to a nonexistent image.

Also I have not been able to find any list of good applications or big enough that use RubyMotion.

And what I did not expect is to see the forum empty. ( Does anyone use rubymotion? )

And many more things like these.

When I remembered that RubyMotion exits and I started reading the documentaicon and doing local tests I thought that I have found the perfect solution, but seeing all these details that make me think that the project is abandoned or only worries about charging the money to the people who use it … Probably I’ll opt for NativeScript or ReactNative.

Any comment? Experience? Or some information that can make me decide for RubyMotion?

The project seems interesting to me but very stopped since 2014.
I do not know if it is abandoned or the person in charge is not very good in marketing.

How does the development of RubyMotion continue?

Any comment or experience would be great.

Thank you in advance.


#2

Most heavy users are over at https://motioneers.herokuapp.com. Join us and say hi.


#3

Yep, it is still here (never went away), and is still being updated. There was a bit of a pause when RubyMotion went through a change of ownership/stewardship, so for the most part I think what you are seeing are third party remnants and the slow update of the widely scattered articles and web pages as Amir has been consolidating things.

This list seems a bit thin due to some problems with the last host (see the pinned Hello World topic) and now everyone is on Slack, but the community has stayed fairly active, as far as toolchains go.

The Ruby language, the object model being almost identical to Objective-C (which the various Cocoa/Cocoa Touch frameworks are still dependent on, despite Swift), drop-in C and Obj-C libraries, and not needing to use the Xcode IDE make RubyMotion a no-brainer for me, and I’m not even a professional developer. YMMV, so it depends on what you are looking for.

As for NativeScript or ReactNative, I suppose that depends on your tastes as well - personally, I think javascript is an ugly language and not fun at all, despite being very popular.


#4

Alive and well :slight_smile:

The forum was rebooted a couple of weeks ago. Here is the archive.


#5

Hi guys,

I am in a similar position as @RTJ, I’ve known about RubyMotion for a few years, and as a Ruby dev I’d love to write mobile apps in Ruby… but the project seems really dead/abandoned by all standards.
Last tweet and blog post were in February 2018 and only a few posts in this forum since March 2018.
Also, you never hear about RubyMotion in the Ruby or webdev community, not a single post like “look at this great app I built with RubyMotion”.
A Slack workspace for support is great, but a bit of “marketing” (or really just signs of life) are much more important. As it is right now, I (and probably a lot of other Ruby devs) won’t use RubyMotion out of fear that we waste our time getting into a system that turns out to be abandoned…


#6

What did you think of the blog entry from February?


#7

It’s great to have guiding principles, but I would find it much more valuable and interesting to read regular blog posts about new features, see new samples (the last update in https://github.com/HipByte/RubyMotionSamples is from Februar 2017) or maybe even a development roadmap for the next months.
Is there any place to see what the current and previous versions are and when they were released?


#8

Maybe it’s useful to dump motion changelog along with a timestamp somewhere, @amirrajan?


#9

This is great feedback. Thank you. I’ve made a note of this and will definitely do a post with each release and what’s coming down the pipe.

I’ll put this on the site somewhere. This is a good idea in general I feel.


#10

@zoopzoop based on your feedback, I’ve posted a new blog entry. Let me know what you think: RubyMotion Moving Forward - One Year Later.

Sincerely speaking, here. Let’s stop this “is RubyMotion is still alive” non-sense
(of course it’s alive, battle hardened, and doing well). Keep the feedback coming. I’ll keep improving the platform and incorporating everything I learn with every new app I release.


#11

Hi @amirrajan,

Thanks, I put my feedback in a Gist since I can only post 2 links per post here as a new member: https://gist.github.com/manuelmeurer/d8f29185b653412ed5d17c6649e18464

Sincerely speaking, here. Let’s stop this “is RubyMotion is still alive” non-sense.

I’m not sure this is the right attitude. It people sign up to this forum to post this question here, it seems to be a valid concern. I know it certainly is for me.
In the end, it’s your project though and your decision how to market it. As you mentioned in the post, you dislike marketing in the conventional sense. I’m not sure RubyMotion will be able to reach it’s full potential without some old-school marketing though… would it be an option to get someone else on board to do the marketing-part? Just an idea…


#12

I’ll add links to the meetup, and repos to the new entry :+1:

As for the repos being part of my personal account, one of RubyMotion’s (my) guiding principals is “People over Entities”. So the repos will continue to stay under my GitHub handle. Again just my personal preference, what’s more official than the CEO/Owner of the company having the repos under him?

I completely understand why you initially posted. The question now is have I addressed that concern? If not, then what else should I update? As I said in the news entry:

If you’re looking for a “safe” commodity toolchain, backed by a “safe” large corporation (who doesn’t care about your success, nor the tiny line-item the toolchain represents on their balance sheet), look elsewhere. RubyMotion isn’t for you. If your sole motivation is to check the “we have a cross-platform mobile app” checkbox for your company, look elsewhere. RubyMotion isn’t for you.

Again, I’m trying my best to keep a firm, kind tone (albeit not very nice). RubyMotion isn’t for everyone. It really is important to me that the people who use RubyMotion are trying to build successful apps in the company of others who have built successful apps (more so than the guise of safety from using a toolchain built by a large corporation).

Let me know what else you’d like to see changed :+1:

Aside: I’m more than happy to have a Hangout session with the decision makers at your company too. And talk about any reservations you may have. Lemme know :tada: