A Buildship overview related to FlutterFlow & my opinion

แชร์
ฝัง

ความคิดเห็น • 27

  • @jwolpert
    @jwolpert 4 หลายเดือนก่อน +1

    I found myself fooling around with buildship after spending time screwing around with flutterflow to handle api keys properly on server side environment variables rather than what most tutorials do putting them into the action flow or (worse) into app state or hardcoded into the api builder in headers. Wrote a cloud function to handle the keys server side. Went so far as to implement secret manager. No joy. Would not deploy. Pretty easy in buildship to set up secret keys and use them (and it is using secret manager on the back end), but yeah…could have saved myself time just doing it all in vs code. If there is a quick and security-compliant way to manage keys in flutterflow, I’d love to see the recipe.

    • @teknesis7339
      @teknesis7339  4 หลายเดือนก่อน +1

      There isn't any way that I know of to adequately store the keys in FF. You'd need access to device level code to store keys but even so, storing keys hard-coded isn't a great idea unless they're user-specific keys that are generated by the user and stored locally.
      As for using secrets manager and cloud functions, that method is actually quite simple, not sure what issues you ran into with that, but it's fairly straightforward (and I believe I've posted a tutorial how to do it). My issue with Buildship is that it's a waste of money and places another point of failure between your app and your API content. Reducing PoFs and costs should be a primary goal for success in app development.

    • @jwolpert
      @jwolpert 4 หลายเดือนก่อน

      Yeah, I thought your argument in the video was compelling. I also used your other video on cloud functions and secret keeper. No joy. For me, at least, I added hours screwing around trying to get this approach to work with FF when it would have taken me about a half hour to do it from scratch with vs code/etc. my reasoning for using FF on this rapid prototyping project was to get through the UI fast, and I like a more wysiwyg approach for that. Definitely buildship’s method for managing api keys took about 30 seconds, so there’s that. But to be clear, that’s not an argument against your points. More that FF might spend some time in future making that as easy and clear as buildship does.

  • @DanVanDamme
    @DanVanDamme 6 หลายเดือนก่อน +2

    Super informative!! Looking forward to your upcoming tutorials on leveraging Flutterflow and cloud functions (Supabase would be my ask) to make API calls. Is there an ETA on the release date for this series? Discord only?

    • @teknesis7339
      @teknesis7339  5 หลายเดือนก่อน +2

      You'll want to keep an eye out for a limited seat course I'm offering soon. We'll be going over everything one would need to know to get their app in public offering shape, including your question.

  • @jacknimmo2926
    @jacknimmo2926 6 หลายเดือนก่อน

    Great videos man, I have a question. Im trying to build a feature where the user has a list of contacts, and the data for each contact is stored locally as its own datatype item in an appstate variable. When you click on a contact it brings you to a page displaying their data. The problem I’m having is I can’t figure out how to make that page reference the data for the specific contact I clicked on. Thank you again 👍

  • @jonloi3794
    @jonloi3794 24 วันที่ผ่านมา

    Isn't Buildship positioned as a backend service to a lowcode frontend like Flutterflow? It's probably better to use something like Buildship vs Zapier or Make tbh, since writing cloud functions in node.js is probably hard for non-devs.

    • @teknesis7339
      @teknesis7339  24 วันที่ผ่านมา

      Life isn't easy.

  • @billshook
    @billshook 2 หลายเดือนก่อน

    Thanks for your candid report.
    Much appreciated.
    Just to hear the answer clearly, what do you recommend for a no code guy like me to use for building my own chatbot apps, instead of BuildShip ?
    Thanks 😊

    • @teknesis7339
      @teknesis7339  2 หลายเดือนก่อน

      If you're planning to stick to the no code trend, then BuildShip is your best bet out of the platforms similar to them.. that's not saying a whole lot but it is what it is. I'd just highly recommend you read and understand their terms of service, because they're quite terrifying.

  • @brynales
    @brynales 4 หลายเดือนก่อน

    Hello, are there any better alternatives to do some more elaborate backenbed functions besides buildship?

    • @teknesis7339
      @teknesis7339  4 หลายเดือนก่อน

      Learn to code in Nodejs and Python. You'll be happy you did

  • @jacknimmo2926
    @jacknimmo2926 6 หลายเดือนก่อน +1

    Also I think build ship is really gonna spark the fire for no-code.

    • @teknesis7339
      @teknesis7339  4 หลายเดือนก่อน

      Unfortunately

  • @billshook
    @billshook 2 หลายเดือนก่อน

    Where can I find info about the “Easter Egg” 😊 Thanks

    • @teknesis7339
      @teknesis7339  2 หลายเดือนก่อน

      I've since redacted this plan out of the very, very, very small amount of respect I have left for BuildShip. Just gonna let this one die I guess.

  • @Dreysimmons
    @Dreysimmons 5 หลายเดือนก่อน

    Please you mentioned how easy it is to securely store your api keys in flutterflow, please can you show me how? Or suggest various ways that can be done? Been trying to find how to do that for a while now

    • @teknesis7339
      @teknesis7339  5 หลายเดือนก่อน +1

      I posted a video a couple weeks back showing how with cloud functions

    • @Dreysimmons
      @Dreysimmons 5 หลายเดือนก่อน

      Ok thanks will check it out @@teknesis7339

  • @Cesarkzz
    @Cesarkzz 6 หลายเดือนก่อน +2

    Most of the people on flutterflow are not devs, thats why we use no-code tools.

    • @teknesis7339
      @teknesis7339  6 หลายเดือนก่อน +12

      And I get that completely. But there's a huge misconception, or perhaps illusion, that solely knowing no-code puts those who use it in the same bracket as those who do know code, and as it stands today, even with increasingly intelligent AI and a plethora of tools that didn't exist five years ago, those who know code are the ones sitting among the upper echelon of the success bracket, which i believe lacks principle and why I aim to shape a different path forward.
      Who's achieving greater success, the ones who build AI from lines of code or the ones who use prebuilt systems? There's an advantage to be had in knowing traditional coding, from standard development practices to getting the most out of AI's capabilities.
      With all of that said, there's a notable gap to be bridged, and that's what I'm trying to do - by demonstrating if you have the dedication and intellect to study no-code, you can also hybridize that with traditional code, leveraging the best of both worlds to position yourself as a viable candidate in this rapidly evolving industry.
      Taking Buildship as an example, trust me, you can do what they offer without their tools. And as an Easter egg to that end, I have a trick I'll be disclosing soon as to how you can leverage Buildship and still cut out the middleman.

    • @Cesarkzz
      @Cesarkzz 6 หลายเดือนก่อน

      @@teknesis7339 You are right, the way to go in my opinion is hybrid. The less time it takes to develop something and having the tools to make it work at a great level. Thanks for your response and your videos. I truly appreciate!

    • @EmblazNOR
      @EmblazNOR 6 หลายเดือนก่อน

      Cant wait for the trick! How to store api keys in firebase or supabase cloud functions?

    • @xzatech
      @xzatech 6 หลายเดือนก่อน

      ​@@EmblazNOR 👍🏾 Nice