SketchCut

Opening the App for the First Time

You install the app, open it, and immediately face a blank table. No tutorial pops up. No welcome screen explains where to start. The interface looks like a spreadsheet from the late 90s. That is the first real moment with SketchCut. You have to figure out that the top fields are for sheet size, cut width, and edge offset. Below that, a table waits for part dimensions. The app does not hold your hand. It expects you to know what you are doing. This is not a casual tool. It is built for people who already understand cutting layouts.

The initial screen shows a grid. You enter the length and width of your sheet material. Then you add parts with their sizes and quantities. The app calculates a cutting plan based on your inputs. It shows you how many sheets you need and where each part goes. The layout appears as a visual map. You can see the cuts drawn out on the sheet. This direct visual feedback is what keeps people using it. One user noted that it saved about 15% more material than their usual method. That is a real number that matters to anyone buying sheets of plywood or MDF.

But the simplicity ends there. The app offers two calculation methods: "By Length" and "By Width." The choice changes how the initial cuts are made. "By Length" cuts along the long side first. "By Width" starts with the short side. The method you pick affects the entire layout. Choose wrong, and you might waste a full sheet. The app does not tell you which is better. It just gives you both options and lets you decide. This is where experience matters.

The Original Analysis – When Methods Clash with the Editor

Here is where things get interesting. The app lets you run the calculation with either method. Then it gives you a layout editor. You can drag parts around manually. This sounds useful. But the editor does not always respect the logic of the method you chose. If you calculate "By Length" and then move parts in the editor, the app does not recalculate the waste percentage. It just lets you rearrange. The original calculation remains fixed. The editor is a separate layer. This creates a disconnect. You might think you are improving the layout, but the app does not update the numbers to reflect your changes. The waste area, the cut length, the edgebanding totals — they stay as they were before your manual edits. This is a limitation that only emerges when you try to use both features together. The Play Store description does not mention this. It presents the editor as a helpful addition. In practice, it is a tool that can mislead you if you are not careful.

This behavior comes from the app's design philosophy. It treats the calculation and the editing as separate steps. The calculation is a one-time event. The editing is a visual adjustment. But for a user, they are part of the same workflow. You calculate, you review, you tweak. The app breaks that flow. It forces you to re-run the calculation after every major edit if you want accurate numbers. That adds time. It also adds frustration. Several users complained about this indirectly. They mentioned that the app "does not make sense" or that it "mixes up" dimensions. The real issue is the split between the calculation engine and the manual editor.

What the Changelog Actually Says

The current version update note says: "Technical update. A new version of the app will be released soon." That is it. No list of bug fixes. No mention of performance improvements. No detail on what changed. The developer has not published specific details about recent changes. This is a pattern. The app has been updated regularly, but the changelog remains vague. Users are left guessing what was fixed or broken. The lack of transparency is a recurring theme in the reviews. People report that after an update, the keyboard stops working. Or that the app crashes more often. But the changelog does not acknowledge these issues. It just says "technical update." This absence of information is itself a piece of information. It tells you that the developer either does not track changes closely, or does not want to share what they are fixing.

Some users have pointed out that the app stopped being compatible with newer Android versions. The last update that added real features might have been months ago. The current updates seem to be maintenance only. But without a clear changelog, you cannot know. You have to rely on user reports. And those reports are mixed. Some say the app works fine. Others say it is broken. The inconsistency suggests that the app behaves differently on different devices or Android versions. This is a common problem for apps that are not actively maintained with clear release notes.

Real-World Performance and Common Issues

The app is free. That is its biggest selling point. But free comes with trade-offs. The Lite version does not support decimal points. This is a critical flaw for anyone working with precise measurements. Plywood comes in fractions. MDF is often specified in millimeters with decimals. Without decimal support, you have to round. Rounding leads to waste. One reviewer called the Lite version "useless for plywood layout." That is a strong statement, but it reflects a real limitation. The PRO version adds decimal support, but it costs money. So the free version is effectively a teaser. It shows you what the app can do, but it handicaps you with missing precision.

Another common issue is data loss. Several users reported that after entering parts, the app freezes. Then it erases all entered data. This happened to multiple people across different devices. One user said it happened three times in a row. Another mentioned that saved files cannot be reopened. These are not minor bugs. They are workflow killers. If you spend 20 minutes entering part dimensions and the app crashes, you lose that time. If you save a project and cannot open it later, you cannot trust the app for real projects. These complaints appear repeatedly in the research. They are not isolated incidents. They are patterns. The app has stability problems that affect its core functionality.

The interface itself is dated. Multiple users compared it to Windows 95 or Windows XP. It works, but it looks old. The buttons are basic. The layout is functional but not polished. For a tool that you might use daily, the visual experience matters. It affects how quickly you can work. A cluttered or outdated interface slows you down. The app gets the job done, but it does not make the process pleasant. This is a trade-off that some users accept. They value the functionality over the aesthetics. But it is worth noting that the app has not received a major visual overhaul in years.

The Editor and the Missing Keyboard

A specific issue that stands out is the keyboard input problem. After certain Android updates, the app stops responding to the keyboard. You tap on a field to enter a number, and nothing happens. The keyboard does not appear. This is a critical failure. You cannot use the app without entering numbers. The only workaround is to restart the app or the device. Some users reported that switching to a different keyboard app helps. But that is not a solution. It is a hack. The developer has not addressed this in any public update note. The changelog does not mention it. So users are left to figure it out on their own. This lack of responsiveness to a major bug erodes trust. It suggests that the developer is not actively monitoring user feedback, or at least not acting on it.

The editor itself has other quirks. When you move a part, the app does not snap to grid or show alignment guides. You have to eyeball it. This is fine for rough adjustments, but it is not precise. For a cutting optimization tool, precision is everything. The editor feels like an afterthought. It was added to give users some control, but it lacks the refinement of a professional layout tool. This is another area where the app's limitations become apparent. It is a good calculator, but it is a poor design tool. The two functions do not integrate well. This is the core of the original analysis. The app is split between a powerful calculation engine and a weak manual editor. The disconnect between them is the source of many user frustrations.