Sahil Seta

I'm Satil Sita. I started my journey from PHP WordPress by developing custom themes and plugins. And then I later gained interest in JavaScript, TypeScript. So I still started logging it, and I got a good opportunity to work on the Angular framework. Then I moved to JavaScript. And during my four-year period, I also got a chance to work with Node.js, React.js, MongoDB, and also with major libraries like Tailwind CSS, Bootstrap, DHTMLX to create schedule Gantt charts and complex data models and views. And, also, I have a good experience working with product-based development, I mean designing and developing the entire product from scratch as well as defining a set of reusable components where I can reuse the view. Use the UI. Yeah. So that was it from my experience.

To manage the interaction between Angular and the front end and back end team, I will definitely help them out with the requirements. Firstly, I need to know all the requirements from my side, what data I need, and then I'll help them with the JSON. Like, the type of JSON is what type of JSON I will require. And I will try to optimize the UI as much as possible to reduce the API calls and the number of APIs to be developed. And also, there are some best practices to follow while integrating the APIs in the front end, such as error handling, which is a major part when someone else is developing the API. I should tell them that if a specific response is not coming from the API or specific key inputs are not coming, they should handle the API errors appropriately and the same should be followed in the front end.

Personally, I will suggest using most of the reusable UI modules, the lazy loading routes to enhance the user experience and reduce the load time. Also, the server-side rendering (SSR) is a good feature to quickly load the first screen, and that will give users a good sign that your website is having an overall very enhanced and genuine user experience. Also, other than this, we should handle all the most of the errors properly. We should flow. We should think like a user while developing the front end. That will be the major aspects. This will be the major effect. Other than this, I will definitely try to optimize the UI as much as possible for most of the screens, like on tablets or mobile phones and laptops. So, that will be from my side, and that will be the best scenario to enhance the overall user experience. Also, we should follow these standard practices while developing the apps, like following the coding best practices and removing unnecessary libraries if there are, and not using libraries for such basic tasks. We should always go for custom development if the application requires critical performance.

PWAs are a good way to provide a user a feature where they can access the application via the browser itself and for their convenience. If they don't want to go to the browser every time to ask for the website, then they can also add them on their mobile screens while using the Progressive Web Apps. It is similar to web view where in the application view, we load the application and your applications with the help of some features. We have some predefined set of libraries. And it is a good feature if we are looking for an ecommerce or a blogging website or something like a user-centric application. So, that will be a good way to expand the user criteria and usability.

So in accordance with my previous answer, the continuous integration process will help us improve the overall quality of the code. Because while we are building, we can't think of the entire scenario and each case where the user will be doing what, including all the user interactions with the application. So while our dev application has completed and is going for testing, after testing, the user will be using the application. During that session, we can follow up with them and get feedbacks on what issues they are facing and what problems they are facing. By this way, by using these feedbacks, we can rapidly improve the application, which will also be a good way to improve the code quality for developers. Because we are continually growing and expanding the application, and its code base as well. Like there will be some real parameters as well, which we can't check during the development phase. So that could be caught in this continuous integration process.

Yeah, here they have used the component design pattern. I mean, the component. There is an app component. There is a class named as an app component. And, in this, there has been a decorator component decorator which has its own property, selector, template, and styles URL. So here, we are not defining the template URL. Instead, we are directly putting the HTML. Not even the HTML, but a string where we are printing a string in the template column, and that includes our variable name which has a value, which is a type of string and has a value as Angular. So it will print "welcome, Angular," and it follows the component-based model. However, there are some certain other patterns which we can use to develop the Angular applications, which is a module-based component where we can provide lazy loading as well if the application is larger in size. But for a smaller number of applications, like for a smaller amount which has 5 to 7 pages or which is not going to handle a large number of data, it is fine to use the component-based.

We have a class named App component, which includes a variable of type string and an ngOnIt. Firstly, we'll come to the ngOnIt. And generally, it is an angular lifecycle hook which is being used to initialize the component with some of its values. Let's suppose if you want to call the API or you want to initialize something or you want to assign some default values to the variables, which we are doing here. We are assigning a value to message by accessing it like this: message is equals to "Hello". We are putting a value as "hello", and we are printing it in our template, an Angular component template. So this is the major role of the ngOnIt method. And the ngOnIt method is something which will be called while the component is being injected in the UI, injected in the screen, and just before the constructor, it will be called. And after each change detection.

Yes, in my past years of experience, I've faced numerous epic problems which were from the UI as well as from the back-end perspective. But, in this question, you asked us to compare Angular with React. So, if we talk about global data management, as we are aware, ReactJS provides a good library, which is Redux, a store-based state management library, used mostly in big-scale applications. The access applications will have this library. But if I talk about Angular, I prefer subjects and behaviors, which are the features of RxJS library. Also, in new Angular versions, we have signals, which is a great way to pass and store data with multiple components and services. So, this is what I would definitely use. And also, Angular in terms of change detection, I faced a lot of issues while implementing the DHTMLX diagram, but I solved it with the change detection. And other than this, I developed some real-time applications where the Microsoft Excel-like feature is developed in a table. User will be able to

Yes, Shirley. This is one of the major features if we talk about SPAs and front-end development. We should always ensure code reusability everywhere during the entire application development. And if we talk about RejS is a component-based library, and Angular is a different thing - it's a full-fledged framework. And generally, a framework defines the way it has a very defined way of working and developing occasions. Generally, in my current organization, we have a product-based company where we have a module shared module where we define the set of reusable components. Like, I have a table, static table where I can part. I can push the columns. I can push the data. I can push the callbacks, which I want to fire when some particular column is being updated. And, also, there are some other components as well, like card, convo view. We have a convo view with where the user can see the data. So, that the usability should be ensured by using input and event emitters in Angular, so we can pass some values. And based on the value, we generate the UI. In the access, it has been used with prompts, which are a great way to pass the data to the child component or a reusable component. And also, these standalone features will