Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More

Memberships

Low-Code Community

Public โ€ข 379 โ€ข Free

Formula

Private โ€ข 306 โ€ข $15/m

6 contributions to Low-Code Community
Client mangament Portal
Hi everyone, I'm looking for recommendations on an all-in-one client management platform that can handle: - Client onboarding - Proposals - Contracts - Time tracking - Invoicing I currently use Hello Bonsai for proposals, agreements, and invoicing, and Timely for time tracking (suggested by a client). However, I find the invoicing process tedious. Ideally, I'm seeking a platform that automates these processes, especially for long-term clients. Please share any suggestions you may have. Thanks in advance!
3
4
New comment 3d ago
0 likes โ€ข 12d
@Halil Faruk Kurt thanks for sharing, i will check these out
1 like โ€ข 3d
@Robert Boulos Thanks for sharing! I'll check out the tool and definitely reach out if I need help with setup.
How to Set Up Stripe Test and Live Mode on Xano Backend/Webhook
Excited to share that I've published my first-ever tech blog! https://likhikaroutray.hashnode.dev/how-to-set-up-stripe-test-and-live-mode-on-xano-backendwebhook It's all about setting up Stripe webhooks with Xano, focusing on how to manage test and live environments seamlessly. If you've ever accidentally processed test payments in a live environment (oops! ๐Ÿ˜…), this one's for you! In the blog, I cover: - Setting up Xano branches and data sources - Configuring Stripe webhooks for different environments - A nifty trick to automate environment detection It's a quick read that could save you some headaches. Check it out if you're working with Stripe and Xano, or just curious about streamlining your dev process! Would love to hear your thoughts or experiences. Drop a comment or share if you found it helpful!
2
0
Toddle.dev
Hello Guys. In the last few weeks, I've been doing a tutorial on Toddle.dev. They seem to be an alternative to Wized, much more visual and, in my opinion, much easier for those of us who are NoCode, understand some Javascript, but struggle with building structures or flow diagrams. Honestly, I find it very powerful and far superior to Wized in many aspects. Has anyone else tried it? Could you share your opinions in comparison with other No Code WebApp Builders?https://toddle.dev/
5
8
New comment 29d ago
2 likes โ€ข 30d
I have tried toddle few weeks back and here are few things from my perspective. The design interface is cool - they have a modular/component development approach similar to how React works. They've got page-level SSR and are working on component-level SSR too. The tool is made keeping developers in mind, and its version control feature is solid. They have plan to go open source in their future plan. But I kind of stopped trying it for now because: No pre-built library to start with(it kind of depends on community around the tool) Not great for quick web app launch/buildThe styling options are a bit limited (though you can add custom CSS) Might give it another shot in a few months, but for now, I'm looking at other options. Hope this helps!
1 like โ€ข 29d
@Alejandro La Moglie I've been checking out weweb lately. They've got some awesome Xano backend integrations built right in. There are also a few UI component libraries you can use. @Daniel Migizi probably knows more about weweb if you want extra details.
What's your favorite Low-Code tool?
We are tech-agnostic here - my view is that the best tool for the job depends on the job. With that being said, what tool do you find yourself using the most? This could include Zapier, N8N, and more! Which of the following tools do you use most frequently in your work?
Poll
11 members have voted
3
14
New comment 15d ago
2 likes โ€ข Aug 28
@Daniel Migizi same here, i was able to build a react project setup along with typescript and node just using cursor. I don't know anything about node or react. It's just so good.
2 likes โ€ข Aug 29
@Daniel Migizi I recently worked on a small POC using Privy.io, a Web3 authentication service, with React and TypeScript. Here's an overview of my process and the challenges I encountered: 1. Initial Setup: I began by using Claude 3.5 Sonnet to obtain the necessary npm commands for the initial setup of a React project. I chose Vite as my build tool for the quick setup process. 2. Vulnerability Issues: During the build process, I encountered numerous vulnerabilities. To address these, I utilized Cursor AI directly within IDE 3. npm Challenges: Initially, I experienced problems with npm. These issues were later resolved after I installed pnpm on my machine. 4. Cursor Assistance: Cursor AI proved to be incredibly helpful. It not only ran commands for me but also wrote code to fix various files. One particular issue I faced was with the package.json file, which Cursor AI successfully resolved without me manually fixing it. Overall, I was able to successfully complete the build process using a combination of Cursor AI and Claude. While I haven't yet created a full demo, I plan to do so in the future coming future :) I stumbled upon a video which explains pretty much all aspects of development with Cursor https://www.youtube.com/watch?v=Rgz6mX93C4Y Hope this helps!!
I've been learning about web security, here are some tips applied to no-code. (most backend, some frontend)
DISCLAIMER: I'm not a security expert at all, so takes everything I say here with a gram of salt and do your own research! Apart from securing your endpoints with security measures (like Xano Auth Tokens), I found some other concerns you may have when building webapps. The easy and basic (no-brainer recommendations): 1. Xano automatically builds CRUD operations (without authentication) for each table you create. Unless you need them, turn that option off (on the new table menu). If you don't, anyone with your Xano URL (which may be obtained from your frontend) can call them (guessing the table name, such as "user" or "payment" or "property" or whatever you called them) and do funny stuff like read all your records, use the ids to delete them, or edit them, or create new ones without any of your logics. 2. Unless you need them to be public, hide all your API docs; same as the past example. If someone has your XANO URL, and you don't turn off your API docs, they have a guide on how to call your APIs on your behalf. This is especially concerning if you don't set authentication for each API that does sensitive stuff, which takes us to the next tip. 3. Secure all your endpoints that return info or do sensitive operations on your backend, but more than that, only return info to an auth token about the id saved inside the auth token. For example, if you have an API that returns the property of a user, don't query by a given user_id on the JSON body, but by the user_id stored on the authtoken! Xano uses JWT encoded tokens, which means that the auth tokens can contain info, and they contain the id of the user by default, so ALWAYS query by that. If you don't, anyone with an authtoken can trigger APIs on behalf of other users just by changing the user_id on the JSON body. 4. Encrypt any sensitive data on your db (such as card numbers, or user identification documents, etc.), or even better, don't save any sensitive data at all. Research if you can make that save payment method process without actually saving the user card details, the majority of vendors (such as Stripe) allow you to handle tokens that represent user payment data, but they handle the actual payment data (and more than probably, they are better at doing so). 5. Be careful with how you save the authtoken on the frontend and give each token a short life (I think the default 1 day is ok for most, but depending on your project, you may require longer or shorter).
3
4
New comment Aug 26
I've been learning about web security, here are some tips applied to no-code. (most backend, some frontend)
2 likes โ€ข Aug 25
great points Juan, Thanks for sharing!! Just to add to the above, adding a tutorial here from the Xano team on securing APIs https://www.youtube.com/watch?v=yv9yGAZKlRs Also, I specifically relate to sanitising form inputs, this can come in handy to prevent form spamming and HTML/JS injections. if you want to add an extra layer of security to prevent XSS attacks you can do that in meta tag as well using CSP, however, that requires a little deeper understanding of how XSS and CSP work you can refer to this article https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
1-6 of 6
Likhika Routray
2
1point to level up
@likhika-routray-3671
WWX developer | No-code enthusiast

Active 1d ago
Joined Aug 21, 2024
India
powered by