DEV Community

Cover image for Why is naming a developer SaaS harder than building it? 😅
Georgi Hristov
Georgi Hristov

Posted on

Why is naming a developer SaaS harder than building it? 😅

I’m building a platform for replaying and debugging production API requests in ASP.NET apps and I’m stuck choosing the name.

Current options:

  1. DebugSandbox
  2. NetSandbox
  3. TraceLive

Update:
Some really good suggestions came from the comments already.

@gimi5555 suggested names around
“Craft” like ResponseCraft

@csm suggested
ServiceCheck / CheckService

Which one sounds best to you?

Or would you suggest something completely different?

Top comments (5)

Collapse
 
csm18 profile image
csm

ServiceCheck
or CheckService

Since, api gives us a service and we are checking it!

Collapse
 
georgi_hristov profile image
Georgi Hristov

That actually sounds pretty solid.
I checked the .com domain price… €21k.

I may have to reconsider my relationship with .dev and .app domains.

text €21K for a domain

Collapse
 
csm18 profile image
csm

Man! You are serious!

I am so glad, that you liked the name!

Collapse
 
gimi5555 profile image
Gilder Miller

Yes, Georgi. The Naming tools is the worst part of building anything. Your ASP.NET replay approach actually solves something I need right now.
What do you think about names with Craft in them? Like ResponseCraft or something... Feels more active than Playground.

Collapse
 
georgi_hristov profile image
Georgi Hristov • Edited

You may be right about that.
“Craft” gives more of a production-tool feeling compared to “Playground”.

I actually split the idea into two separate projects.

The first one is already launched — DebugProbe for ASP.NET Core:

DebugProbe

Nuget package

GitHub

The SaaS/replay platform is still in planning phase, but once I finalize the direction I’ll start building it properly.
ResponseCraft definitely sounds closer to the direction I want.