--- title: "Checklists before a project starts" description: "What you settle or supply before a project starts: legal details, domain, brand, content and process, for a website, an online shop and an app." locale: "en" canonical: "https://jomaha.studio/en/docs/checklists" updated: "2026-10-22T22:25:17.777Z" site: "jomaha.studio" --- # Checklists What you settle or supply before a project starts: for a website, an online shop and an app. Not everything has to be decided on day one, but every open item moves the launch. Take the list for your project and tick off what is already settled; we go through the rest together. ## Website ### Business and legal - [ ] Company name, legal form, address, authorised representative (for the Impressum) - [ ] Commercial register entry, VAT ID, chamber or supervisory authority, where they exist - [ ] Impressum and privacy policy: from a generator (e.g. IT-Recht Kanzlei, eRecht24) or a law firm - [ ] Third-party services that process data (maps, booking, newsletter, analytics): each needs a paragraph in the privacy policy ### Domain and email - [ ] The domain, and whether it is registered (where, and who has access) - [ ] The mailbox that receives contact-form enquiries - [ ] An existing site: who has access, and which pages must stay reachable (redirects) ### Brand - [ ] Logo as a vector file (SVG, PDF or AI), if one exists - [ ] Colours and typefaces, if defined - [ ] Two or three sites you like, and what you like about them ### Content - [ ] Who writes the copy, and by when - [ ] Languages: German only, or German and English - [ ] Form of address: the informal “du” or the formal “Sie” - [ ] Photos: your own, a shoot, or stock - [ ] References and testimonials, with permission from the people named - [ ] A blog: only if someone keeps it up. Otherwise I leave it out ### Process - [ ] One contact person who signs off on drafts - [ ] The target launch date - [ ] Who maintains the site after launch ## Online shop A shop needs everything a website does, with one difference: some of it is legally required before the first parcel ships. ### Business and legal - [ ] Company name, legal form, address, authorised representative (for the Impressum and the GPSR manufacturer details) - [ ] Business registration, VAT ID; small-business scheme (§ 19 UStG) yes or no - [ ] Legal texts: Impressum, privacy policy, terms, withdrawal notice, shipping and payment information. From a legal-text service (e.g. IT-Recht Kanzlei, Händlerbund) or a law firm - [ ] Registration in the LUCID packaging register, before the first parcel - [ ] Product safety warnings where needed (GPSR) ### Selling - [ ] Delivery area: Germany only, DACH, or the EU - [ ] Shipping: carrier, cost per country, free-shipping threshold - [ ] Returns: who pays return shipping, and where returns go - [ ] Payment: a Stripe account in your company’s name (cards, Apple Pay, Google Pay, others on request) ### Products - [ ] A product list with name, description, price, variants (size, colour …) and stock - [ ] Product photos, ideally consistent and bright - [ ] The categories your customers browse by ### Domain and email - [ ] The domain, and whether it is registered (where, and who has access) - [ ] A sender address for order emails and a mailbox for customer questions - [ ] An existing shop: customers, orders and products to migrate ### Brand and content - [ ] Logo as a vector file (SVG, PDF or AI), colours and typefaces, if they exist - [ ] Two or three shops you like, and what you like about them - [ ] Copy for home, about and contact; form of address “du” or “Sie” ### Process - [ ] One contact person who signs off on drafts - [ ] The target launch date, with a test order using real payment before it - [ ] Who processes orders and maintains the shop after launch ## App An app mostly needs accounts and responsibilities in your name. Which of them apply depends on whether the app goes into the stores or runs in the browser. ### Platforms - [ ] Which platforms: iOS, Android, web, or a combination - [ ] Whether the app goes into the App Store and Google Play, or a web app in the browser is enough - [ ] Whether older devices or tablets have to be supported ### Store accounts - [ ] An Apple Developer account and a Google Play developer account, both in your company’s name, not mine - [ ] A D-U-N-S number for your company: both stores require one for an organisation account, and getting it can take a few days - [ ] Access for me in both accounts, so I can upload test builds - [ ] Who pays the store fees: yearly at Apple, once at Google ### Sign-in - [ ] Whether users need an account at all - [ ] If so, how they sign in: email and password, a link by email, with Apple or with Google - [ ] Anyone who can create an account must be able to delete it in the app. Both stores require this - [ ] Roles: whether there are, say, admins, staff and customers with different rights ### Notifications - [ ] Push notifications: yes or no, and what for - [ ] What sends them: automatically (e.g. on a new booking) or by hand - [ ] The service that delivers them (on Android usually Google’s Firebase Cloud Messaging) belongs in the privacy policy ### Privacy - [ ] A privacy policy at a public address: both stores require the link - [ ] The App Store’s privacy details and Google Play’s Data safety section: which data the app collects, and what for - [ ] Third-party services in the app (analytics, crash reports, maps, payment): each needs a line in the privacy policy and in the store details ### Backend and data - [ ] Which data the app stores, and whether it has to stay in Germany or the EU - [ ] Existing systems the app connects to (inventory, CRM, website) - [ ] Who needs access to the data in day-to-day work, e.g. through an admin panel - [ ] Whether the app has to work without an internet connection ### Release and upkeep - [ ] Who publishes new versions in the stores: you or me - [ ] The store listing: app name, description, screenshots, icon and a support address - [ ] Testers who try a test build before launch (TestFlight at Apple, internal testing at Google Play) - [ ] One contact person who signs off on drafts - [ ] The target launch date, with time for the stores’ review - [ ] Who maintains the app after launch: the stores regularly require updates for new operating system versions