Since your backend will likely expose its functionality over HTTP, you can definitely use PHP in combination with Dart/Flutter. You can use whatever as your backend.
Since Flutter is backed by Google, you get lots of great functionality out-of-the box if you are using Firebase as your backend though. You can even get very far without writing any backend-code. I would recommend having a look at that as well.
Developing a managed multivendor marketplace mobile app to enable users to buy and sell (mainly used hardware) products from the same app, allowing buyers to checkout and purchase an entire listing at either the set "buy now" price or "make offer" to buy at a negotiated price with the seller. Please share your opinion on my current choice Flutter + Laravel (with MySQL) and are there more feasible alternatives?
Just use the language you're most proficient and can iterate quickly with - of a, perhaps, larger concern - where is your backend?
Sure, you may be leveraging other services but I presume you're still going to log information about transactions and whatnot
My Situation: I am both
Working on a startup/side hustle app, an interactive fitness journal that tracks and recommends exercise as well as makes creating meal plans trivial, in Flutter where the back-end will tentatively be written using Django REST framework as a REST API. For what it's worth Microsoft Azure will be my cloud of choice.
I'm also trying to transition away from an on-prem senior engineer to a Cloud Engineer.
Flutter is a firm choice for the FE however I'd really appreciate some guidance on which tools I should consider using to be in line with contemporary cloud languages and tools as well, if it is a good idea to suck it up and put Python on the back burner so I can learn JavaScript. I need things like ORMs, User Auth, etc.
Can anyone please advise?
I like to use nodejs with prisma ORM, you can also use Typescript, its very easy to learn and Prisma provides a own studio that helps you with the database; another option is PHP with Laravel with the Eloquent ORM, or you can still in your current stack, anyways i recommend you to use Redis from cache database, this will make your app or website very fast
I need to build a virtual trading website for a client. I'm considering Next.js for the frontend but can't decide whether to use FastAPI or Django as the backend.
I'll use PostgreSQL for the database. Also, there will be a Mobile version of the website using Flutter. It needs to be able to connect with the backend.
Any advice is greatly appreciated.
While I personally tend to favor FastAPI for my projects, I think Django is the right choice for many. You'll get more feature out of the box, including an ORM, which should allow you to develop your project faster. FastAPI is indeed fast, but utilizes async Python that may be unfamiliar to some devs. Django also has added some async features recently, and those are optional. Also, while FastAPI is great for APIs because it can auto-generate your API docs for you, it sounds like you are not going to have a public API so this may not be needed in your project. And Django has plugins like Django Rest Framework to help create nice REST API endpoints.
I want to point that, you can still have a fullstack app with next.js with T3 Stack (Next.js + tRPC + TypeScript + Prisma) so your api/server is collocated with your front-end. You can prototype quickly and pivot after to all first if your app grow
I'm planning a social media mobile app. I would like to prototype using a cross-platform native solution, leaving room for a future web client. In mobile dev, I'm most experienced with Flutter but I use Next.js for web projects. Since I'm not a designer, I think material 3 would be a fair design system and it's integrated into Flutter. React Native does not have material 3 yet but it would allow an easier web implementation (I have found flutter web to be too slow)
What do you suggest?
I think this is a good choice, so many design elements are considered for you such that even if you're not a great designer, as long as you're focused on layout and functionality it's relatively trival to go in later and apply themes and custom widgets. I'm using flutter for the same reasons as you it sounds like and for what it's worth people have been extremely pleased with the tools I've built for them even though I didn't really consider design. Knowing I don't have to worry about making things pretty for them to be attractive to end users is a huge boon for me and I hope it can be for you as well.
RE Flutter Web, I'm sure it will improve with time, I've only ever really seen it slow when it's first starting up. but once the app is "loaded" into the web server so to speak, it's generally been pretty performant assuming I'm doing things like caching appropriately.
Thank you for your response, I appreciate the time you took to reply with certainly useful information.
Hello,
I'm in the midst of reviewing an old CRUD SAAS I have running on Angular 7 with a MariaDB backend and Laravel PHP. Presently is hosted on a couple of Linode servers- and really feeling the weight, especially with the looming need to upgrade to A15 and meet the pace and scalability occurring (for context, the SAAS turns in over 24k USD monthly in subscriptions- so I have concerns around the impact of a new stack on existing clients). Additionally, I manage a Kotlin and Swift codebase for appdev.
I'm looking at moving towards Flutter for a singular codebase, and something serverless but still relational- like Supabase. In the past, I ran my own Auth services- but it was a ton of work to setup and maintain, so looking at using Firebase for Auth services (I know Supabase has Auth as well, but I wonder if it's as reliable and frequently maintained as Firebase?) Supabase has a FlutterSDK as well which makes things much simpler. Planning on maintaining microservices like Stripe etc for functional aspects.
I would love some insight from those who have done a tech stack transition, what should I be aware of- those who have produced in Flutter or a similar stack, what am I walking into without knowing?
Hi, I am making a website and mobile app for service providers of my region to share their profiles and make posts and interact with the clients, I am considering using Vue.js because it's simple and great for working in teams; node in the backend and Flutter and Dart in the mobile app, with MySQL database, do you guys think that its a solid stack for a scalable website and app?
I am interested in using a chat SDK for a community mobile Flutter app. I am between SendBird and Stream. I currently have 2,000 monthly active users and plan to have close to 5,000 active users chatting on the app. Has anyone used either and had good/bad experiences? Currently, there is no chat functionality, and we would like to have a 1-to-1 user chat, group chat, and large community chat capabilities.
Hi, Tom! I'd recommend Stream's Flutter SDK if scalability and performance for a growing number of active users are your focus!
Here's an honest comparison of the two: https://getstream.io/blog/product-comparison-stream-vs-sendbird/
And here are a few case studies on Stream customers who switched from Sendbird: - https://getstream.io/blog/hio-switched-from-sendbird-to-stream/ - https://getstream.io/blog/pluang-uses-stream-chat/
Here are some of the top blogs on building chat with Stream's Flutter SDK that might help you decide: - https://getstream.io/blog/build-a-flutter-social-chat/ - https://getstream.io/blog/creating-a-fast-and-beautiful-chat-with-flutter/
And of course, always feel free to reach out to our sales team to learn more: https://getstream.io/contact/
Hello,
We're just brainstorming for the moment and we have a few questions.
We have an idea for an app that we want to develop, here are the prerequisites:
1) cross-platform (iOS, Android, and website);
2) as easy to maintain as possible / well documented / widely used;
3) Visual Studio Code and Copilot compatible;
4) Text to speech;
5) Speech recognition;
6) Running in background (screen off with TTS and speech recognition);
7) could be using TypeScript;
8) Monetized through ad and in-App payment for premium version;
9) Display on lock screen (Android only I guess)
So what would you recommend?
I've been trying to review the options available, and I've considered:
NativeScript
React Native
Flutter
Any other?
Thanks in advance for your help, and I'm open to any comments.
Use Flutter and Firebase as a backend service, Firebase also helps to speed up the development and rollout of the app. The cloud-hosted NoSQL database provides a real-time database that helps you store and synchronize data between the clients. This indeed makes it easier for you to access the data using any of the devices.
Thanks, is it possible to develop in typescript with flutter?
Currently, I'm working as a frontend dev. I work with Angular. Also, have experience with Dart/Flutter. To learn some tools for the backend, what should I choose ASP.NET Core or Spring Boot?
Given Angular is written in TypeScript, C# will feel more familiar to you. Other reasons to choose ASP.NET are that it's one of the fastest frameworks out there for any language, has a lower learning curve compared to Spring Boot, allows you to quickly build JSON Web APIs and uses less memory. Another notable option if you have a lot of TypeScript code you wish to reuse is Nest framework, which is a TypeScript framework that uses the same architecture as Angular but for back end APIs. I would still choose ASP.NET over Nest but it depends on what will give you more benefits.
Thanks,
I already started learning ASP.NET.
Got a course on udemy: "Build an app with ASPNET Core and Angular from scratch".
Given you have cross platform experience (dart, angular) I would recommend spring boot. It is a powerful platform, allows you to easily integrate with many standard tools: databases, message queues, … And you have the freedom to deploy your applications on every platform that has Java or containers available - so virtually everywhere.
I advise you to go for spring boot: it's the future. Just look at the statistics: spring boot is far more used and spread.
It's very easy to use, easy to install, easy to learn.
You'll not regret it!
