StackShare uses Rails
The first live version of Leanstack was actually a WordPress site. There wasn’t a whole lot going on at first. We had static pages with static content that needed to be updated manually. Then came the concept of user-generated content and we made the switch to a full on Rails app in November of last year. Nick had a lot of experience with Rails so that made the decision pretty easy. But I had also played around with Rails previously and was comfortable working with it. I also knew I’d need to hire engineers with a lot more experience building web apps than I do, so I wanted to go with a language and framework other people would have experience with. Also, the sheer number of gems and tools available for Rails is pretty amazing (shout to RubyToolbox ).
I don’t see us ever having to move away from Rails really, but I could be wrong. Leanstack was built in Rails 3. For StackShare we decided to upgrade to Rails 4. Biggest issue with that has been caching. DHH decided to remove the standard page and action caching in favor of key-based caching (source)[http://edgeguides.rubyonrails.org/caching_with_rails.html#page-caching]. Probably a good thing from a framework-perspective. But pretty shitty to have to learn about that after testing out your new app and realizing nothing is cached anymore :( We’ll need to spend some more time implementing "Russian Doll Caching", but for now we’ve got a random mixture of fragment and action caching (usually one or the other) based on which pages are most popular.
Karma uses Rails
We use Rails for webpages and projects, not for backend services. Actually if you click through our website, you won't notice it but you're clicking though, I think, seven or eight different Rails projects. We tie those all together with a front-end library that we wrote, which basically makes sure that you have a consistent experience over all these different Rails apps.
It's a gem, we call it Karmeleon. It's not a gem that we released. It's an internal gem. Basically what it does is it makes sure that we have a consistent layout across multiple Rails apps. Then we can share stuff like a menu bar or footer or that kind of stuff.
So if we start a new front end project it's always a Rails application. We pull in the Karmeleon gem with all our styling stuff and then basically the application is almost ready to be deployed. That would be an empty page, but you would still have top bar, footer, you have some custom components that you can immediately use. So it kind of bootstraps our entire project to be a front end project.
Instacart uses Android SDK
So we very, very early on, we were iOS only, then we thought, well we’re missing out on half of the market. We need to add Android. So we had a friend of ours start working on the Android app, and I had to build the API for him, but I was having a really hard time doing that because I didn’t know what he needed exactly, so I built the first version of the web store over the weekend because I wanted to have a client to consume myself for the API I was building.
Instacart uses Rails
Web has always been in Rails from the beginning, so we used Redis for caching our items, which we had, from the beginning. Rails is kind of what we were comfortable with, and we knew we wanted the front end to be really, really snappy, so we de-normalized all the item attributes into Redis, and that's how it got served out.
megmorsie uses CodeIgniter
I used CodeIgniter while working at KHM Travel Group. It was the system we used for an affiliate-based site called TravSearch, which I later replaced with a WordPress Multisite. I developed a .csv upload form to transfer all the information from the affiliate table of CodeIgniter to the user and options tables in WPMU.
toolmantim uses Rails
Rails 5 (beta 3) provided a nice structure for rendering responses, linking to front-end assets (compiled previously via Webpack), handling sessions w/ tailor made login links via an email button/token, background jobs, and creating an admin behind basic auth to allow managing of users and purchases.
Ngakkan Nyaagu uses Rails
For this project rails was ideal due to new features introduced in Rails 5 that allowed us to build a lightweight "API only" project. Developer familiarity and the ability to rapidly iterate, as well as providing an accessible testing framework were additional factors.
anasancho uses Android SDK
Self taught : acquired knowledge or skill on one's own initiative. Unity and app compatible porposes : software development kit that enables developers to create applications for the Android platform.
gllona uses CodeIgniter
CodeIgniter is the MVC framework used for the PHP coding. Also, validation criteria for (database) table fields are the provided by CodeIgniter, and signatures for others are derived from those.
Scrayos UG (haftungsbeschränkt) uses Android SDK
The Android SDK is the key-component of all Android-based development and had to be included in this stack for sure. We work with the SDK through IntelliJ IDEA and the command-line.
papaver uses Android SDK
last time i used the android sdk was converting the tiktok app to ios. what a mess it was back then. the developer nature of the sdk was apparent vs apples offering.
Grupo Gamma Peninsular, SA de CV uses Android SDK
Uso del Android SDK para el desarrollo de aplicaciones para Android con geolocalizaciĂłn, multimedia y almacenamiento en la base de datos.
delbin uses CodeIgniter
It is super easy to do things in PHP using codeigniter. Used the MVC architecture to create different types of pages and modules.