Kintone gave our operations team enough control to adjust forms, add fields, and refine views without turning every small request into a development ticket. That independence is useful, but we learned fairly quickly that no-code does not mean no governance. During the first few months, too many people had permission to change applications, and the result was predictable: duplicate fields, inconsistent naming, and formulas that only made sense to the person who created them. We eventually assigned an owner to each app, introduced conventions for field codes, and added a review step before changes reached production. Lookup and Related Records have been especially valuable when several workflows depend on the same information. Instead of copying the client, project, technical owner, and contract type into every new record, we pull those values from the source app and display linked requests, incidents, or deliveries inside the main record. To non-technical users, it feels like they are working in a single system. Underneath, we can still keep separate apps with cleaner responsibilities and avoid turning one giant form into the company’s entire operating model. Review collected by and hosted on G2.com.
Kintone gives us enough visual flexibility for internal applications, but it starts showing its limits when the experience needs to feel highly tailored. Fields, groups, tables, and spacing are easy enough to arrange, but precise control over labels, responsive behavior, layouts, or interactive components usually means adding JavaScript, CSS, or a plug-in. We ran into that while building an app for field technicians. The team wanted every piece of information visible on a single screen so they would not have to move through tabs or extra steps, and we tried to accommodate it. The form technically worked, but it became dense, slower to scan, and harder to use on smaller screens. We spent some time trying to improve it with CSS before accepting that the problem was not the styling. The structure itself was overloaded. Simplifying the form and showing only the information technicians needed at each stage produced a much better result than continuing to decorate a layout that had already become too complicated. Review collected by and hosted on G2.com.
