Alternatives to API Platform logo

Alternatives to API Platform

Laravel, Symfony, Lumen, Slim, and Node.js are the most popular alternatives and competitors to API Platform.
66
93
+ 1
7

What is API Platform and what are its top alternatives?

It is a set of tools to build and consume web APIs. You can build a fully-featured hypermedia or GraphQL API in minutes. Leverage its awesome features to develop complex and high performance API-first projects. Extend or override everything you want.
API Platform is a tool in the Frameworks (Full Stack) category of a tech stack.

Top Alternatives to API Platform

  • Laravel

    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

  • Symfony

    Symfony

    It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP.. ...

  • Lumen

    Lumen

    Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching. ...

  • Slim

    Slim

    Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself. ...

  • Node.js

    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Django

    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • ASP.NET

    ASP.NET

    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...

  • Android SDK

    Android SDK

    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. ...

API Platform alternatives & related posts

Laravel logo

Laravel

20.4K
16.2K
3.5K
A PHP Framework For Web Artisans
20.4K
16.2K
+ 1
3.5K
PROS OF LARAVEL
  • 514
    Clean architecture
  • 374
    Growing community
  • 348
    Composer friendly
  • 323
    Open source
  • 303
    The only framework to consider for php
  • 202
    Mvc
  • 195
    Quickly develop
  • 159
    Dependency injection
  • 147
    Application architecture
  • 134
    Embraces good community packages
  • 62
    Write less, do more
  • 55
    Restful routing
  • 52
    Orm (eloquent)
  • 47
    Artisan scaffolding and migrations
  • 47
    Database migrations & seeds
  • 36
    Awesome
  • 34
    Great documentation
  • 26
    Awsome, Powerfull, Fast and Rapid
  • 25
    Promotes elegant coding
  • 25
    Build Apps faster, easier and better
  • 22
    Easy to learn, scalability
  • 22
    JSON friendly
  • 21
    Eloquent ORM
  • 21
    Modern PHP
  • 21
    Most easy for me
  • 20
    Test-Driven
  • 19
    Blade Template
  • 18
    Beautiful
  • 13
    Security
  • 12
    Based on SOLID
  • 11
    Simple
  • 11
    Clean Documentation
  • 11
    Cool
  • 10
    Easy to attach Middleware
  • 10
    Convention over Configuration
  • 9
    Easy Request Validatin
  • 8
    Easy to use
  • 8
    Its just wow
  • 8
    Simpler
  • 8
    Get going quickly straight out of the box. BYOKDM
  • 8
    Laravel + Cassandra = Killer Framework
  • 8
    Fast
  • 7
    Less dependencies
  • 7
    Friendly API
  • 7
    Super easy and powerful
  • 7
    Simplistic , easy and faster
  • 6
    Great customer support
  • 6
    Its beautiful to code in
  • 5
    The only "cons" is wrong! No static method just Facades
  • 5
    Fast and Clarify framework
  • 5
    Active Record
  • 5
    Php7
  • 5
    Speed
  • 5
    Easy
  • 4
    Composer
  • 4
    Laravel Mix
  • 4
    Minimum system requirements
  • 4
    Easy views handling and great ORM
  • 4
    Eloquent
  • 4
    Laragon
  • 3
    Laravel Nova
  • 3
    Laravel casher
  • 3
    Laravel Passport
  • 3
    Ease of use
  • 3
    Cashier with Braintree and Stripe
  • 3
    Laravel Forge and Envoy
  • 3
    Laravel Horizon and Telescope
  • 3
    Laravel Spark
  • 3
    Intuitive usage
  • 2
    Heart touch
  • 2
    Like heart beat
  • 2
    Rapid development
  • 2
    Laravel love live long
  • 2
    Touch heart artisan
  • 2
    Scout
CONS OF LARAVEL
  • 42
    PHP
  • 28
    Too many dependency
  • 20
    Slower than the other two
  • 16
    A lot of static method calls for convenience
  • 13
    Too many include
  • 10
    Heavy
  • 7
    Bloated
  • 6
    Laravel
  • 5
    Confusing
  • 4
    Does not work well for file uploads in Shared Hosting
  • 4
    Too underrated
  • 2
    Not fast with MongoDB
  • 1
    Difficult to learn
  • 1
    Not using SOLID principles

related Laravel posts

I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

Need help deciding technology stack. Thanks.

See more
Antonio Sanchez

Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

See more
Symfony logo

Symfony

5.6K
4.2K
1.1K
A PHP full-stack web framework
5.6K
4.2K
+ 1
1.1K
PROS OF SYMFONY
  • 172
    Open source
  • 144
    Php
  • 125
    Dependency injection
  • 125
    Community
  • 117
    Professional
  • 76
    Doctrine
  • 70
    Organized
  • 65
    Modular architecture
  • 44
    Smart programming
  • 40
    Solid
  • 17
    Documentation
  • 13
    LTS releases
  • 8
    Robust
  • 8
    Easy to Learn
  • 7
    Good practices guideline
  • 7
    Bundle
  • 7
    Decoupled framework components
  • 6
    Service container
  • 6
    Simple
  • 4
    Powerful
  • 3
    Flexible
CONS OF SYMFONY
  • 9
    Too many dependency
  • 7
    Lot of config files
  • 3
    YMAL
  • 2
    Feature creep
  • 1
    Bloated

related Symfony posts

Benjamin Bernard-Bouissières

I really love Django because it is really fast to create a web application from scratch and it has a lot a facilities like the ORM or the Admin module ! The Python language is really easy to read and powerful, that's why I prefer Django over Symfony.

I use Django at work to make tools for the technicians but I also use it for me to build my personal website which I host on PythonAnywhere, and with a domain name bought on Namecheap.

See more
Samuel Webster
Principal Developer at Colart · | 7 upvotes · 206.7K views

We needed our e-commerce platform (built using WooCommerce) to be able to keep products in sync with our #pim (provided by #akeneo) which is built in Symfony . We hooked into the kernel.event_listener to send RabbitMQ messages to a WordPress API endpoint that triggers the updated product to rebuild with fresh data.

See more
Lumen logo

Lumen

375
563
152
The stunningly fast PHP micro-framework by Laravel
375
563
+ 1
152
PROS OF LUMEN
  • 33
    API
  • 25
    Microframework
  • 19
    MVC
  • 16
    PHP
  • 12
    Open source
  • 11
    Eloquent
  • 10
    Restful & fast framework
  • 7
    Illuminate support
  • 7
    Composer
  • 4
    Brother of laravel and fast
  • 4
    Easy to learn
  • 4
    Fast
CONS OF LUMEN
  • 3
    Not fast
  • 2
    PHP
  • 1
    Not fast with MongoDB

related Lumen posts

Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Aimad Quouninich

Hello everyone,

I have a final-study project, and I'm responsible for making decisions for what frameworks to use (both front-end and back-end) and the software architecture to adapt.

The project is a web application for a concrete company. The main goal is to calculate what is called OEE (Overall Equipment Effectiveness), meaning simply the efficiency of the machine. The calculation and display of OEE will be in real-time, meaning that this rate will be updated every two minutes, and it will appear in a graph. Also, we have the state of the machines to display whether the machines are working just fine or there is some problem.

This will be done using IoT, meaning that important data will be sent from the machine to the web application that I will create via the API (someone else will be responsible for this matter). Of course, the application will include employees, factories, as well as machines, ... etc.

The most important thing in the application is real-time performance monitoring of machines and the OEE.

A real example of what we want to do => https://evocon.com/

I choose to use Laravel because : - This type of applications could be implemented by Laravel - Me and my colleague have some knowledge and practice with this framework (choosing other technologies like Node.js means a huge learning curve) - Easy documentation and abandon tutorials

The only reason why I choose Vue.js because It goes well with Laravel (from what I have learned).

The second important question, which software architecture should I adapt ? should I use Microservice Architecture or the normal and well-known Monolithic Architecture? I know the benefits and disadvantages of the first and second methods, but I do not want to make a wrong decision.

If I choose microservice for this project, I will use Lumen (PHP Micro-Framework By Laravel).

Should I use micro-frontend as well? Like VuMS, or it's not necessary for this project?

I don't think that the reasons to choose Laravel are enough, so I want to understand the obstacles that I may face during the development.

In the end, I decided to ask and take expert opinions.

NOTE: this web application will be used by other companies, like in the case of evocon.

If there are tips and things that I must know to accomplish this project, please mention them.

Thank you very much.

See more
Slim logo

Slim

247
334
135
A PHP micro framework
247
334
+ 1
135
PROS OF SLIM
  • 29
    Microframework
  • 26
    API
  • 21
    Open source
  • 19
    Php
  • 11
    Fast
  • 8
    Restful & fast framework
  • 7
    Easy Setup, Great Documentation
  • 5
    Good document to upgrade from previous version
  • 5
    Clear and straightforward
  • 4
    Modular
CONS OF SLIM
    Be the first to leave a con

    related Slim posts

    Y. Taborda
    Shared insights
    on
    PHPPHPLumenLumenYiiYiiSlimSlim

    I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.

    But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.

    Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?

    How do you suggest to make the test to prove wich one is better?

    PHP Lumen Yii Slim

    See more
    Node.js logo

    Node.js

    125K
    103.5K
    8.4K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    125K
    103.5K
    + 1
    8.4K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 795
      Open source
    • 484
      Great for apis
    • 474
      Asynchronous
    • 420
      Great community
    • 390
      Great for realtime apps
    • 295
      Great for command line utilities
    • 81
      Node Modules
    • 80
      Websockets
    • 67
      Uber Simple
    • 57
      Great modularity
    • 56
      Allows us to reuse code in the frontend
    • 40
      Easy to start
    • 35
      Great for Data Streaming
    • 31
      Realtime
    • 26
      Awesome
    • 24
      Non blocking IO
    • 17
      Can be used as a proxy
    • 16
      High performance, open source, scalable
    • 15
      Non-blocking and modular
    • 14
      Easy and Fun
    • 12
      Easy and powerful
    • 12
      Same lang as AngularJS
    • 11
      Future of BackEnd
    • 10
      Fast
    • 9
      Fullstack
    • 9
      Scalability
    • 9
      Cross platform
    • 8
      Simple
    • 7
      Mean Stack
    • 6
      Great for webapps
    • 6
      Easy concurrency
    • 5
      Friendly
    • 5
      Fast, simple code and async
    • 5
      React
    • 4
      Great speed
    • 4
      Fast development
    • 4
      Its amazingly fast and scalable
    • 4
      Control everything
    • 4
      Easy to use and fast and goes well with JSONdb's
    • 4
      Typescript
    • 4
      Scalable
    • 3
      It's fast
    • 3
      Easy to use
    • 3
      Isomorphic coolness
    • 2
      Sooper easy for the Backend connectivity
    • 2
      Easy to learn
    • 2
      TypeScript Support
    • 2
      Scales, fast, simple, great community, npm, express
    • 2
      One language, end-to-end
    • 2
      Javascript2
    • 2
      Not Python
    • 2
      Performant and fast prototyping
    • 2
      Blazing fast
    • 2
      Great community
    • 2
      Less boilerplate code
    • 2
      Easy
    • 1
      Lovely
    • 1
      Event Driven
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 42
      New framework every day
    • 35
      Lots of terrible examples on the internet
    • 29
      Asynchronous programming is the worst
    • 23
      Callback
    • 16
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      Dependency hell
    • 10
      Low computational power
    • 7
      Can block whole server easily
    • 6
      Very very Slow
    • 6
      Callback functions may not fire on expected sequence
    • 3
      Unneeded over complication
    • 3
      Unstable
    • 3
      Breaking updates
    • 1
      No standard approach

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 1.7M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 39 upvotes · 4.2M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Django logo

    Django

    26.6K
    23.5K
    3.8K
    The Web framework for perfectionists with deadlines
    26.6K
    23.5K
    + 1
    3.8K
    PROS OF DJANGO
    • 634
      Rapid development
    • 468
      Open source
    • 401
      Great community
    • 353
      Easy to learn
    • 263
      Mvc
    • 215
      Beautiful code
    • 210
      Elegant
    • 193
      Free
    • 191
      Great packages
    • 178
      Great libraries
    • 68
      Restful
    • 65
      Comes with auth and crud admin panel
    • 65
      Powerful
    • 60
      Great documentation
    • 58
      Great for web
    • 44
      Python
    • 37
      Great orm
    • 34
      Great for api
    • 27
      All included
    • 22
      Web Apps
    • 21
      Fast
    • 18
      Used by top startups
    • 16
      Clean
    • 15
      Easy setup
    • 15
      Sexy
    • 12
      Convention over configuration
    • 10
      ORM
    • 9
      The Django community
    • 9
      Allows for very rapid development with great libraries
    • 6
      Great MVC and templating engine
    • 6
      King of backend world
    • 6
      Its elegant and practical
    • 5
      Mvt
    • 5
      Batteries included
    • 5
      Full stack
    • 5
      Fast prototyping
    • 5
      Easy Structure , useful inbuilt library
    • 5
      Easy to develop end to end AI Models
    • 5
      Have not found anything that it can't do
    • 4
      Very quick to get something up and running
    • 4
      Easy to use
    • 4
      Easy
    • 4
      Cross-Platform
    • 3
      Map
    • 3
      Great peformance
    • 3
      Scaffold
    • 3
      Just the right level of abstraction
    • 3
      Modular
    • 3
      Full-Text Search
    • 3
      Zero code burden to change databases
    • 3
      Python community
    • 3
      Many libraries
    • 2
      Easy to change database manager
    • 1
      Node js
    CONS OF DJANGO
    • 25
      Underpowered templating
    • 19
      Underpowered ORM
    • 19
      Autoreload restarts whole server
    • 15
      URL dispatcher ignores HTTP method
    • 10
      Internal subcomponents coupling
    • 7
      Admin
    • 7
      Not nodejs
    • 6
      Configuration hell
    • 4
      Not as clean and nice documentation like Laravel
    • 3
      Python
    • 3
      Not typed
    • 3
      Bloated admin panel included
    • 2
      Overwhelming folder structure
    • 1
      InEffective Multithreading

    related Django posts

    Dmitry Mukhin

    Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

    Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

    For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

    However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

    All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

    See more

    Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

    See more
    ASP.NET logo

    ASP.NET

    21.4K
    6.7K
    14
    An open source web framework for building modern web apps and services with .NET
    21.4K
    6.7K
    + 1
    14
    PROS OF ASP.NET
    • 11
      Great mvc
    • 3
      Easy to learn
    CONS OF ASP.NET
    • 1
      Not highly flexible for advance Developers
    • 1
      Entity framework is very slow

    related ASP.NET posts

    Greg Neumann

    Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

    This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

    But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

    I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

    Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

    See more

    Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

    We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

    We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

    ASP.NET / Node.js / Laravel. ......?

    Please guide us

    See more
    Android SDK logo

    Android SDK

    19.7K
    14.8K
    786
    An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
    19.7K
    14.8K
    + 1
    786
    PROS OF ANDROID SDK
    • 285
      Android development
    • 153
      Necessary for android
    • 127
      Android studio
    • 85
      Mobile framework
    • 81
      Backed by google
    • 26
      Platform-tools
    • 21
      Eclipse + adt plugin
    • 4
      Powerful, simple, one stop environment
    • 2
      Free
    • 2
      Больно
    CONS OF ANDROID SDK
      Be the first to leave a con

      related Android SDK posts

      Jesus Dario Rivera Rubio
      Telecomm Engineering at Netbeast · | 10 upvotes · 858.6K views

      We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

      Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

      We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

      You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

      See more
      Sezgi Ulucam
      Developer Advocate at Hasura · | 7 upvotes · 667.4K views

      I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

      The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

      See more