How software licensing works
A software license is a record of permission to use your product. The license key is the value your customer presents so your app can find and check that permission. The key itself is not the plan, expiry or device limit: those details are stored with the license on the server.
Follow a license for MyApp
You sell a 30-day Professional license for MyApp. In the dashboard, you create the license, choose Professional, set its duration and allow two devices. You send the key to the customer. The value could be generated, or it could be your own custom string such as ADE.
What the plan does
Professional can provide defaults such as PDF export enabled and 4K previews. The license still has its own expiry, device bindings and individual overrides. Your app reads the effective values after login. Assigning a plan name alone does not automatically implement paid features in your code.
Expiry and first use
You can use a specific expiry date or, where configured, begin a duration on the first successful login. A 30-day duration that starts on first login should not lose days while the unused key sits in a customer’s inbox. A fixed expiry date is different: access ends at that date even if the customer starts late.
Read the actual expiry returned by the server instead of calculating a fresh 30 days at every launch. A successful login today does not promise access forever. Check the active session and respond to changes.
Remembering a key
A Remember me option belongs to your application’s interface. It can save a key or another supported protected state so the customer does not type it every time. Saving the value does not extend access and should not bypass server checks. Do not store customer credentials in a public or unprotected file.
Licenses and usernames
License login can be the only method you offer, or it can sit beside username and password and device login. Some products let the customer register a username using a license; others keep all access directly on license records. Check the registration behaviour before designing that flow.
What licensing can and cannot protect
Licensing makes access manageable: you can issue permission, set its term and revoke it. A customer can still inspect and modify software running on their own machine. Keep valuable server operations protected on your backend, verify signed responses, and make your program actually enforce rejection results.
Use a test license before issuing a batch. Test the right key, a wrong key, expiry, pause, ban, the device limit and session revocation. Include an outage test so a connection problem is handled differently from an explicit access rejection.

