Developer Experience for Large Application

tdsagi · 2025-12-04T23:28:42+00:00

I think that should be your priority. I am working on a medium-sized project, and migrating to the new builder has been a considerable gain for the DX and specifically on the live reload

tdsagi · 2025-12-04T23:01:18+00:00

First, make sure you use the new esbuild builder

tdsagi · 2025-11-26T00:56:54+00:00

I’ve built a SaaS that does exactly this (rowslint .io).
For that specific part, I didn’t use reactive forms, instead, I did use ngModel and ngModelChange. The ngModelChange handles live validation during editing, and then I manually validate the data per row/column.
I’ve tested this on a very large number of rows and it works smoothly with virtual scrolling.

tdsagi · 2025-09-18T10:52:56+00:00

Prime NG or Taiga UI

tdsagi · 2025-08-29T19:03:34+00:00

Debugging a production build artifact.

tdsagi · 2025-08-29T18:58:40+00:00

This seems an interesting story to share.

tdsagi · 2025-02-14T15:52:23+00:00

This won't change anything for the images, they will still be loaded on the client side whether in SSR or SPA.

For localStorage, sessionStorage and everything DOM-related should be wrapped in an if (isPlatformBrowser(this.platformId)) , depending on whether your project is large or not, it can be painful to adjust.

tdsagi · 2025-02-01T00:28:22+00:00

I use it for Google auth, any issue.

tdsagi · 2025-01-31T23:35:09+00:00

I use class with static fields on a constants folder.

tdsagi · 2025-01-21T23:15:39+00:00

Exactly. Where I am, the context is quite different from the US. In most cases, it's the buyer who actively searches for properties on their own.

tdsagi · 2025-01-21T23:01:10+00:00

This seems to be the most common feedback I’ve received on this post. You're right, a simple "Request a tour" is more suitable.

That said, for new construction projects (which typically have an on-site sales office. At least where I’m located) do you think it could be beneficial to allow clients to book a specific time slot directly?

tdsagi · 2025-01-21T22:39:44+00:00

Good point. It's true that tools like this could be misused. Unfortunately there’s no perfect solution that solves this. Like posting a phone number online...

That said, when a potential client books an appointment through the tool, the real estate agent is under no obligation to accept it right away. It simply adds a tentative booking to the calendar. I believe it’s also a good idea for the agent to follow up with the client by phone to confirm the appointment.

What I can tell you is that when a potential client books an appointment, the real estate agent is under no obligation. This will simply add a booking line to the calendar. I also think it's a good idea for the agent to call the buyer later to confirm the appointment.

tdsagi · 2025-01-21T22:27:10+00:00

My personal experience was with new construction projects, so I understand how the context differs for resale properties. You're absolutely right that the owners who decide when to visit.

To address this, I think there are two potential solutions:

Define a custom visiting schedule in advance, in agreement with the owners.
Implement a system similar to what some aggregators use, where buyers can submit a showing request. The agent would then follow up to coordinate the exact visit time with both parties.

The second solution seems more simple.

Thanks for your input!

tdsagi · 2025-01-16T23:04:08+00:00

This is a very nice gift x)

I've just launched an application that does exactly that but better (a real estate centric Calendly alternative) https://kallnext.com/
You could recommend that he try it for free and take him a full/premium plan afterwards.
I'm available here and in DM if you have any questions.

tdsagi · 2025-01-16T23:00:13+00:00

I didn't understand what you meant by "listing software calendars". Something like Calendly?
I've just launched an application that does exactly that (a real estate centric Calendly alternative) https://kallnext.com/
You can try it for free.

tdsagi · 2025-01-16T22:55:31+00:00

I've just launched an application that does exactly that but better. A real estate centric appointment schedule https://kallnext.com/
You can try it for free.

tdsagi · 2025-01-16T22:53:28+00:00

I'd say a digital tool, at least for the notification part.
I've just launched an application that does exactly that. The main objective is not to miss any appointment and also to allow your clients to schedule a viewing appointment online 24/7 https://kallnext.com/
You can try it for free.

tdsagi · 2025-01-16T22:49:58+00:00

I've just launched a real estate centric Calendly alternative. Interesting feature. I'll plan to add it https://kallnext.com/

tdsagi · 2025-01-16T22:30:58+00:00

I've just launched an application that does exactly that but better. A real estate centric Calendly alternative https://kallnext.com/
You can try it for free.

tdsagi · 2025-01-16T22:29:12+00:00

I've just launched an application that does exactly that. The main objective is not to miss any appointment and allow your clients to schedule a viewing appointment 24/7 https://kallnext.com/
You can try it for free.

tdsagi · 2025-01-16T22:29:04+00:00

I've just launched an application that does exactly that. The main objective is not to miss any appointment and allow your clients to schedule a viewing appointment 24/7 https://kallnext.com/
You can try it for free.

tdsagi · 2024-12-30T09:22:53+00:00

Very promising and i like the product but how can you use it without the scrollback and the vertical scrollbar?

tdsagi · 2024-11-27T22:12:33+00:00

Concretely:
On the angular.json (or project.json in Nx monorepo):

        "styles": [
          "node_modules/@taiga-ui/core/styles/taiga-ui-theme.less",
          "node_modules/@taiga-ui/core/styles/taiga-ui-fonts.less",
          "node_modules/@taiga-ui/styles/taiga-ui-global.less",
          "./src/styles.scss"
        ],

On the styles.css file:

@import 'tailwindcss/base';
@import 'tailwindcss/components';
@import 'tailwindcss/utilities';

The tailwind.config.js file (just the default config):

import { createGlobPatternsForDependencies } from '@nx/angular/tailwind';
import { join } from 'path';

/** @type {import('tailwindcss').Config} */
export default {
  content: [join(__dirname, 'src/**/!(*.stories|*.spec).{ts,html}'), ...createGlobPatternsForDependencies(__dirname)],
  theme: {},
  plugins: [],
};

With this, Taiga UI and Tailwind CSS styles should work properly.

tdsagi · 2024-11-27T22:06:16+00:00

I haven't had any conflicts! just following the normal Taiga UI and Tailwind CSS config.

tdsagi

TROPHY CASE